juicycleff/ultimate-backend

Docker not building api-admin

dmitrijs-pavlovs-dev opened this issue · 1 comments

Hello, thanks for this amazing proof of concept. I am considering of using it in our next big project. But having difficulty with running project locally via docker-compose.

$ docker-compose --project-directory=. -f docker-compose.dev.yml up --build
Building api-admin
Step 1/15 : FROM node:12-alpine
 ---> 1c342643aa5c
Step 2/15 : ARG NODE_ENV=production
 ---> Using cache
 ---> d96d53c896f6
Step 3/15 : ENV NODE_ENV $NODE_ENV
 ---> Using cache
 ---> 2be4f126daef
Step 4/15 : ARG NODE_OPTIONS=--max_old_space_size=4096
 ---> Using cache
 ---> f959a425712a
Step 5/15 : ENV NODE_OPTIONS $NODE_OPTIONS
 ---> Using cache
 ---> 967aa219d20d
Step 6/15 : RUN mkdir -p /nest
 ---> Using cache
 ---> 0de7b5663b67
Step 7/15 : ADD . /nest
 ---> Using cache
 ---> 8aea53b3bf31
Step 8/15 : WORKDIR /nest
 ---> Using cache
 ---> f635447004b8
Step 9/15 : RUN yarn global add @nestjs/cli
 ---> Using cache
 ---> fdaea75ef8c9
Step 10/15 : RUN yarn install --production=false
 ---> Running in 4eea7f95a445
yarn install v1.22.4
[1/4] Resolving packages...
[2/4] Fetching packages...
info fsevents@2.1.2: The platform "linux" is incompatible with this module.
info "fsevents@2.1.2" is an optional dependency and failed compatibility check. Excluding it from installation.
info fsevents@1.2.11: The platform "linux" is incompatible with this module.
info "fsevents@1.2.11" is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
warning "@apollo/gateway > apollo-graphql@0.4.1" has incorrect peer dependency "graphql@^14.2.1".
warning "@apollo/gateway > apollo-server-core > graphql-tag@2.10.3" has incorrect peer dependency "graphql@^0.9.0 || ^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0".
warning "apollo-server > graphql-tools@4.0.7" has incorrect peer dependency "graphql@^0.13.0 || ^14.0.0".
warning "@apollo/gateway > apollo-server-core > graphql-upload@8.1.0" has incorrect peer dependency "graphql@0.13.1 - 14".
warning "@apollo/gateway > apollo-server-core > graphql-tools > apollo-link@1.2.13" has incorrect peer dependency "graphql@^0.11.3 || ^0.12.3 || ^0.13.0 || ^14.0.0".
warning "@apollo/gateway > apollo-server-core > graphql-tools > apollo-utilities@1.3.3" has incorrect peer dependency "graphql@^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0".
warning " > @nestcloud/boot@0.6.11" has incorrect peer dependency "@nestjs/common@^6.0.0".
warning " > @nestcloud/brakes@0.6.11" has incorrect peer dependency "@nestjs/common@^6.0.0".
warning " > @nestcloud/config@0.6.11" has incorrect peer dependency "@nestjs/common@^6.0.0".
warning " > @nestcloud/consul@0.6.11" has incorrect peer dependency "@nestjs/common@^6.0.0".
warning " > @nestcloud/consul@0.6.11" has unmet peer dependency "consul@^0.34.1".
warning " > @nestcloud/feign@0.6.11" has incorrect peer dependency "@nestjs/common@^6.0.0".
warning " > @nestcloud/loadbalance@0.6.11" has incorrect peer dependency "@nestjs/common@^6.0.0".
warning " > @nestcloud/loadbalance@0.6.11" has unmet peer dependency "consul@^0.30.0".
warning " > @nestcloud/grpc@0.6.11" has incorrect peer dependency "@nestjs/microservices@^6.1.1".
warning " > @nestcloud/http@0.6.10-0" has incorrect peer dependency "@nestjs/common@^6.0.0".
warning " > @nestcloud/kubernetes@0.6.11" has unmet peer dependency "kubernetes-client@^8.3.3".
warning " > @nestcloud/logger@0.6.11" has incorrect peer dependency "@nestjs/common@^6.0.0".
warning " > @nestcloud/memcached@0.6.11" has incorrect peer dependency "@nestjs/common@^6.0.0".
warning " > @nestcloud/proxy@0.6.11" has incorrect peer dependency "@nestjs/common@^6.0.0".
warning " > @nestcloud/redis@0.6.11" has incorrect peer dependency "@nestjs/common@^6.0.0".
warning " > @nestcloud/service@0.6.11" has incorrect peer dependency "@nestjs/common@^6.0.0".
warning " > @nestcloud/service@0.6.11" has unmet peer dependency "consul@^0.34.1".
warning " > @nestjs/cqrs@6.1.0" has incorrect peer dependency "@nestjs/common@^6.0.0".
warning " > @nestjs/cqrs@6.1.0" has incorrect peer dependency "@nestjs/core@^6.0.0".
warning " > @nestjs/cqrs@6.1.0" has incorrect peer dependency "reflect-metadata@0.1.12".
warning "apollo-server > graphql-subscriptions@1.1.0" has incorrect peer dependency "graphql@^0.10.5 || ^0.11.3 || ^0.12.0 || ^0.13.0 || ^14.0.0".
warning " > graphql-passport@0.6.3" has unmet peer dependency "subscriptions-transport-ws@0.x".
warning " > graphql-passport@0.6.3" has unmet peer dependency "ws@7.x || 6.x".
warning " > nestjs-eventstore@1.4.14" has incorrect peer dependency "@nestjs/common@^6.0.0".
warning " > nestjs-eventstore@1.4.14" has incorrect peer dependency "@nestjs/core@^6.0.0".
warning " > nestjs-stripe@0.4.0" has incorrect peer dependency "@nestjs/common@^6.0.0".
warning " > nestjs-stripe@0.4.0" has incorrect peer dependency "@nestjs/core@^6.0.0".
warning " > nestjs-stripe@0.4.0" has incorrect peer dependency "stripe@^8.0.0".
warning " > type-graphql@0.18.0-beta.16" has incorrect peer dependency "graphql@^14.6.0".
warning "type-graphql > graphql-query-complexity@0.4.1" has incorrect peer dependency "graphql@^0.13.0 || ^14.0.0".
[4/4] Building fresh packages...
$ yarn run snyk-protect
yarn run v1.22.4
$ snyk protect
Successfully applied Snyk patches

Done in 130.38s.
Done in 391.39s.
Removing intermediate container 4eea7f95a445
 ---> a2dbbc51c37b
Step 11/15 : RUN nest build proto-schema
 ---> Running in 0532669ee88d
Starting type checking service...
Gracefully stopping... (press Ctrl+C again to force)
Hash: f3d3ce9cc5014f105899
Version: webpack 4.42.1
Time: 293934ms
Built at: 06/06/2020 2:29:53 PM
Entrypoint main = libs/proto-schema/index.js
Removing intermediate container 0532669ee88d
 ---> 1e7364a6604c
Step 12/15 : RUN nest build api-admin
 ---> Running in 29cd462f0c61
Starting type checking service...

Then the process just hands there and nothing happens. Not sure if repo issue or just doing something wrong. Any advice ?

@dayrim this issue most times results as a result of the docker server resource size. This has nothing to do with the software itself. You can just use run the app manually. I'm looking to improve the response as well as the docs too are currently in progress. With each milestone drastically reducing the lines of code :)