Reply to thread

Message

<blockquote data-quote="MayoMayn" data-source="post: 438886" data-attributes="member: 71840">So currently I have a mono repository that consists of the structure:[CODE]+-- project|&nbsp;&nbsp; +-- client|&nbsp; &nbsp; &nbsp;&nbsp; +-- assets|&nbsp; &nbsp; &nbsp;&nbsp; +-- src|&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; +-- ...|&nbsp; &nbsp; &nbsp;&nbsp; +-- package.json|&nbsp; &nbsp; &nbsp;&nbsp; +-- angular.json|&nbsp; &nbsp; &nbsp;&nbsp; +-- tsconfig.json|&nbsp; &nbsp; &nbsp;&nbsp; +-- Dockerfile|&nbsp; &nbsp; &nbsp;&nbsp; +-- ...|&nbsp;&nbsp; +-- server|&nbsp; &nbsp; &nbsp;&nbsp; +-- database|&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; +-- ...|&nbsp; &nbsp; &nbsp;&nbsp; +-- src|&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; +-- ...|&nbsp; &nbsp; &nbsp;&nbsp; +-- package.json|&nbsp; &nbsp; &nbsp;&nbsp; +-- .graphqlconfig.yml|&nbsp; &nbsp; &nbsp;&nbsp; +-- tsconfig.json|&nbsp; &nbsp; &nbsp;&nbsp; +-- tsconfig.build.json|&nbsp; &nbsp; &nbsp;&nbsp; +-- Dockerfile|&nbsp; &nbsp; &nbsp;&nbsp; +-- ...+-- yarn.lock+-- package.json+-- lerna.json+-- tsconfig.json+-- tsconfig.base.json+-- docker-compose.yml[/CODE]And the problem is, that the docker-compose services commands can't figure out the workdirs of the images, so it tries to run the script commands in the root directory of the project.Tried to do switch out the bash command with ls and it was still in the root directory of the project.project/server/Dockerfile[SPOILER][CODE]FROM node:alpineARG NODE_ENV=developmentENV NODE_ENV=${NODE_ENV}WORKDIR /usr/app/serverCOPY ./package.json .# COPY ../../yarn.lock .RUN yarnCOPY . .EXPOSE 4242[/CODE][/SPOILER]project/client/Dockerfile[SPOILER][CODE]FROM node:alpineARG NODE_ENV=developmentENV NODE_ENV=${NODE_ENV}WORKDIR /usr/app/clientCOPY ./package.json .# COPY ../../yarn.lock .RUN yarnCOPY . .EXPOSE 8080[/CODE][/SPOILER]docker-compose.yml[SPOILER][CODE]version: '3'volumes:&nbsp; postgres:services:&nbsp; prisma:&nbsp; &nbsp; image: prismagraphql/prisma:1.16&nbsp; &nbsp; restart: always&nbsp; &nbsp; ports:&nbsp; &nbsp; &nbsp; - '4466:4466'&nbsp; &nbsp; environment:&nbsp; &nbsp; &nbsp; PRISMA_CONFIG: |&nbsp; &nbsp; &nbsp; &nbsp; port: 4466&nbsp; &nbsp; &nbsp; &nbsp; databases:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; default:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; connector: postgres&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; host: postgres&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; port: 5432&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; user: prisma&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; password: prisma&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; migrations: true&nbsp; postgres:&nbsp; &nbsp; image: postgres:10.5&nbsp; &nbsp; restart: always&nbsp; &nbsp; environment:&nbsp; &nbsp; &nbsp; POSTGRES_USER: prisma&nbsp; &nbsp; &nbsp; POSTGRES_PASSWORD: prisma&nbsp; &nbsp; volumes:&nbsp; &nbsp; &nbsp; - postgres:/var/lib/postgresql/data&nbsp; client:&nbsp; &nbsp; container_name: emerald-client&nbsp; &nbsp; command: yarn start&nbsp; &nbsp; restart: unless-stopped&nbsp; &nbsp; image: client&nbsp; &nbsp; build:&nbsp; &nbsp; &nbsp; context: ./project/client&nbsp; &nbsp; &nbsp; dockerfile: Dockerfile&nbsp; &nbsp; &nbsp; args:&nbsp; &nbsp; &nbsp; &nbsp; - NODE_ENV=development&nbsp; &nbsp; ports:&nbsp; &nbsp; &nbsp; - '3030:3030'&nbsp; &nbsp; volumes:&nbsp; &nbsp; &nbsp; - .:/usr/app/client&nbsp; server:&nbsp; &nbsp; container_name: emerald-server&nbsp; &nbsp; command: [sh, -c, 'yarn run prisma deploy &amp;&amp; yarn start:dev']&nbsp; &nbsp; restart: unless-stopped&nbsp; &nbsp; image: server&nbsp; &nbsp; depends_on:&nbsp; &nbsp; &nbsp; - prisma&nbsp; &nbsp; &nbsp; - postgres&nbsp; &nbsp; build:&nbsp; &nbsp; &nbsp; context: ./project/server&nbsp; &nbsp; &nbsp; dockerfile: Dockerfile&nbsp; &nbsp; &nbsp; args:&nbsp; &nbsp; &nbsp; &nbsp; - NODE_ENV=development&nbsp; &nbsp; ports:&nbsp; &nbsp; &nbsp; - '4242:4242'&nbsp; &nbsp; volumes:&nbsp; &nbsp; &nbsp; - .:/usr/app/server[/CODE][/SPOILER]Error log[SPOILER][CODE]marcus-sa@DESKTOP-FUHH564:/e/Git/nest-prisma-angular-docker$ docker-compose up --build --remove-orphansBuilding clientStep 1/9 : FROM node:alpine&nbsp;---&gt; 5ffbcf1d9932Step 2/9 : ARG NODE_ENV=development&nbsp;---&gt; Running in 0fa11a29b762Removing intermediate container 0fa11a29b762&nbsp;---&gt; a943a9eaa495Step 3/9 : ENV NODE_ENV=${NODE_ENV}&nbsp;---&gt; Running in 95e18bc28566Removing intermediate container 95e18bc28566&nbsp;---&gt; 349ada5022a1Step 4/9 : WORKDIR /usr/app/client&nbsp;---&gt; Running in be4b60c56e33Removing intermediate container be4b60c56e33&nbsp;---&gt; ad0c66dbfb9dStep 5/9 : COPY ./package.json .&nbsp;---&gt; 4db7715d4607Step 6/9 : RUN yarn&nbsp;---&gt; Running in 5c04efc3e1adyarn install v1.9.4warning package.json: No license fieldinfo No lockfile found.warning @npa/client@0.0.1: No license field[1/4] Resolving packages...[2/4] Fetching packages...(node:1) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.info fsevents@1.2.4: The platform &quot;linux&quot; is incompatible with this module.info &quot;fsevents@1.2.4&quot; is an optional dependency and failed compatibility check. Excluding it from installation.[3/4] Linking dependencies...warning &quot;@angular-devkit/build-angular &gt; @ngtools/webpack@6.2.2&quot; has unmet peer dependency &quot;typescript@~2.4.0 || ~2.5.0 || ~2.6.0 || ~2.7.0 || ~2.8.0 || ~2.9.0&quot;.warning &quot; &gt; @angular/compiler-cli@6.1.7&quot; has unmet peer dependency &quot;typescript@&gt;=2.7.2 &lt;2.10&quot;.warning &quot;@angular/compiler-cli &gt; tsickle@0.32.1&quot; has unmet peer dependency &quot;typescript@&gt;=2.4.2 &lt;2.10&quot;.warning &quot; &gt; apollo-angular@1.3.0&quot; has unmet peer dependency &quot;apollo-link@^1.0.0&quot;.warning &quot; &gt; apollo-angular-link-http@1.2.0&quot; has unmet peer dependency &quot;apollo-link@^1.0.0&quot;.warning &quot; &gt; apollo-angular-link-http@1.2.0&quot; has unmet peer dependency &quot;graphql@^0.11.3 || ^0.12.3 || ^0.13.0&quot;.warning &quot;apollo-angular-link-http &gt; apollo-angular-link-http-common@1.2.0&quot; has unmet peer dependency &quot;apollo-link@^1.0.0&quot;.warning &quot;apollo-angular-link-http &gt; apollo-angular-link-http-common@1.2.0&quot; has unmet peer dependency &quot;graphql@^0.11.3 || ^0.12.3 || ^0.13.0&quot;.warning &quot; &gt; apollo-cache-inmemory@1.2.10&quot; has unmet peer dependency &quot;graphql@0.11.7 || ^0.12.0 || ^0.13.0&quot;.warning &quot; &gt; apollo-client@2.4.2&quot; has unmet peer dependency &quot;graphql@^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0&quot;.warning &quot;apollo-client &gt; apollo-link@1.2.3&quot; has unmet peer dependency &quot;graphql@^0.11.3 || ^0.12.3 || ^0.13.0 || ^14.0.0&quot;.[4/4] Building fresh packages...success Saved lockfile.Done in 39.46s.Removing intermediate container 5c04efc3e1ad&nbsp;---&gt; 1390d02cb152Step 7/9 : COPY . .&nbsp;---&gt; 66ce4136a1c7Step 8/9 : EXPOSE 8080&nbsp;---&gt; Running in c308b6ef13faRemoving intermediate container c308b6ef13fa&nbsp;---&gt; 288e619440e4Step 9/9 : RUN set -ex;&nbsp; &nbsp;&nbsp; if [&quot;$NODE_ENV&quot; = &quot;production&quot;]; then&nbsp; &nbsp; &nbsp; &nbsp;&nbsp; yarn build:prod&nbsp; &nbsp;&nbsp; fi;&nbsp;---&gt; Running in 3211c43f09c6/bin/sh: syntax error: unexpected end of file (expecting &quot;fi&quot;)ERROR: Service 'client' failed to build: The command '/bin/sh -c set -ex;&nbsp; &nbsp;&nbsp; if [&quot;$NODE_ENV&quot; = &quot;production&quot;]; then&nbsp; &nbsp; &nbsp; &nbsp;&nbsp; yarn build:prod&nbsp; &nbsp;&nbsp; fi;' returned a non-zero code: 2marcus-sa@DESKTOP-FUHH564:/e/Git/nest-prisma-angular-docker$ docker-compose up --build --remove-orphansBuilding clientStep 1/9 : FROM node:alpine&nbsp;---&gt; 5ffbcf1d9932Step 2/9 : ARG NODE_ENV=development&nbsp;---&gt; Using cache&nbsp;---&gt; a943a9eaa495Step 3/9 : ENV NODE_ENV=${NODE_ENV}&nbsp;---&gt; Using cache&nbsp;---&gt; 349ada5022a1Step 4/9 : WORKDIR /usr/app/client&nbsp;---&gt; Using cache&nbsp;---&gt; ad0c66dbfb9dStep 5/9 : COPY ./package.json .&nbsp;---&gt; Using cache&nbsp;---&gt; 4db7715d4607Step 6/9 : RUN yarn&nbsp;---&gt; Using cache&nbsp;---&gt; 1390d02cb152Step 7/9 : COPY . .&nbsp;---&gt; bfdd009dc792Step 8/9 : EXPOSE 8080&nbsp;---&gt; Running in b50726163591Removing intermediate container b50726163591&nbsp;---&gt; 78fa6f2af004Step 9/9 : RUN set -ex;&nbsp; &nbsp;&nbsp; if [&quot;$NODE_ENV&quot; = &quot;production&quot;]; then&nbsp; &nbsp; &nbsp; &nbsp;&nbsp; yarn build:prod;&nbsp; &nbsp;&nbsp; fi;&nbsp;---&gt; Running in 54b5e0bea7e3+ '[development' '=' production]/bin/sh: [development: not foundRemoving intermediate container 54b5e0bea7e3&nbsp;---&gt; 9a3b15ea99b3Successfully built 9a3b15ea99b3Successfully tagged client:latestBuilding serverStep 1/9 : FROM node:alpine&nbsp;---&gt; 5ffbcf1d9932Step 2/9 : ARG NODE_ENV=development&nbsp;---&gt; Using cache&nbsp;---&gt; a943a9eaa495Step 3/9 : ENV NODE_ENV=${NODE_ENV}&nbsp;---&gt; Using cache&nbsp;---&gt; 349ada5022a1Step 4/9 : WORKDIR /usr/app/server&nbsp;---&gt; Running in 97c12e798c88Removing intermediate container 97c12e798c88&nbsp;---&gt; b9d853e03877Step 5/9 : COPY ./package.json .&nbsp;---&gt; e9ce8755780bStep 6/9 : RUN yarn&nbsp;---&gt; Running in ba56cf48b5a8yarn install v1.9.4warning package.json: No license fieldinfo No lockfile found.warning @npa/server@0.0.1: No license field[1/4] Resolving packages...[2/4] Fetching packages...(node:1) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.info fsevents@1.2.4: The platform &quot;linux&quot; is incompatible with this module.info &quot;fsevents@1.2.4&quot; is an optional dependency and failed compatibility check. Excluding it from installation.[3/4] Linking dependencies...warning &quot;@nestjs/graphql &gt; merge-graphql-schemas@1.5.4&quot; has incorrect peer dependency &quot;graphql@^0.11.7 || ^0.13.0&quot;.warning &quot; &gt; graphql-tools@3.1.1&quot; has incorrect peer dependency &quot;graphql@^0.13.0&quot;.warning &quot;apollo-server-express &gt; graphql-subscriptions@0.5.8&quot; has incorrect peer dependency &quot;graphql@^0.10.5 || ^0.11.3 || ^0.12.0 || ^0.13.0&quot;.warning &quot;apollo-server-express &gt; apollo-server-core &gt; graphql-tag@2.9.2&quot; has incorrect peer dependency &quot;graphql@^0.9.0 || ^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0&quot;.warning &quot;apollo-server-express &gt; @apollographql/apollo-upload-server@5.0.3&quot; has incorrect peer dependency &quot;graphql@^0.13.1&quot;.warning &quot;prisma &gt; prisma-cli-core@1.0.79&quot; has incorrect peer dependency &quot;graphql@^0.12.0 || ^0.13.0&quot;.warning &quot; &gt; prisma-binding@2.1.5&quot; has incorrect peer dependency &quot;graphql@^0.11.0 || ^0.12.0 || ^0.13.0&quot;.warning &quot;prisma-binding &gt; apollo-link@1.2.2&quot; has incorrect peer dependency &quot;graphql@^0.11.3 || ^0.12.3 || ^0.13.0&quot;.warning &quot;prisma-binding &gt; graphql-import@0.5.2&quot; has incorrect peer dependency &quot;graphql@^0.11.0 || ^0.12.0 || ^0.13.0&quot;.warning &quot;prisma-binding &gt; graphql-tools@3.1.0&quot; has incorrect peer dependency &quot;graphql@^0.13.0&quot;.warning &quot;prisma-binding &gt; subscriptions-transport-ws@0.9.8&quot; has incorrect peer dependency &quot;graphql@^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.1&quot;.warning &quot;prisma-binding &gt; graphql-binding@2.2.4&quot; has incorrect peer dependency &quot;graphql@^0.11.0 || ^0.12.0 || ^0.13.0&quot;.warning &quot;prisma-binding &gt; graphql-binding &gt; graphql-import@0.5.3&quot; has incorrect peer dependency &quot;graphql@^0.11.0 || ^0.12.0 || ^0.13.0&quot;.[4/4] Building fresh packages...success Saved lockfile.Done in 36.16s.Removing intermediate container ba56cf48b5a8&nbsp;---&gt; 6da36da96c51Step 7/9 : COPY . .&nbsp;---&gt; 5cbf9f43aaf3Step 8/9 : EXPOSE 4242&nbsp;---&gt; Running in 3b724af3f3a4Removing intermediate container 3b724af3f3a4&nbsp;---&gt; dc2f82318399Step 9/9 : RUN set -ex;&nbsp; &nbsp;&nbsp; if [&quot;$NODE_ENV&quot; = &quot;production&quot;]; then&nbsp; &nbsp; &nbsp; &nbsp;&nbsp; yarn build;&nbsp; &nbsp;&nbsp; fi;&nbsp;---&gt; Running in 7d318d723049+ '[development' '=' production]/bin/sh: [development: not foundRemoving intermediate container 7d318d723049&nbsp;---&gt; a37ec2260c27Successfully built a37ec2260c27Successfully tagged server:latestStarting nest-prisma-angular-docker_prisma_1&nbsp;&nbsp; ... doneRecreating nest-prisma-angular-docker_client_1 ... doneStarting nest-prisma-angular-docker_postgres_1 ... doneRecreating nest-prisma-angular-docker_server_1 ... doneAttaching to nest-prisma-angular-docker_prisma_1, nest-prisma-angular-docker_postgres_1, emerald-client, emerald-serverpostgres_1&nbsp; | 2018-09-18 22:00:27.700 UTC [1] LOG:&nbsp; listening on IPv4 address &quot;0.0.0.0&quot;, port 5432postgres_1&nbsp; | 2018-09-18 22:00:27.700 UTC [1] LOG:&nbsp; listening on IPv6 address &quot;::&quot;, port 5432emerald-client | yarn run v1.9.4emerald-server | yarn run v1.9.4postgres_1&nbsp; | 2018-09-18 22:00:27.738 UTC [1] LOG:&nbsp; listening on Unix socket &quot;/var/run/postgresql/.s.PGSQL.5432&quot;postgres_1&nbsp; | 2018-09-18 22:00:27.786 UTC [26] LOG:&nbsp; database system was interrupted; last known up at 2018-09-18 21:50:54 UTCemerald-client | error Command &quot;start&quot; not found.emerald-client | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.emerald-server | $ /usr/app/server/node_modules/.bin/prisma deployemerald-server | /bin/sh: /usr/app/server/node_modules/.bin/prisma: not foundemerald-server | error Command failed with exit code 127.emerald-server | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.postgres_1&nbsp; | 2018-09-18 22:00:28.911 UTC [26] LOG:&nbsp; database system was not properly shut down; automatic recovery in progresspostgres_1&nbsp; | 2018-09-18 22:00:28.924 UTC [26] LOG:&nbsp; invalid record length at 0/1677BC0: wanted 24, got 0postgres_1&nbsp; | 2018-09-18 22:00:28.924 UTC [26] LOG:&nbsp; redo is not requiredpostgres_1&nbsp; | 2018-09-18 22:00:29.040 UTC [1] LOG:&nbsp; database system is ready to accept connectionspostgres_1&nbsp; | 2018-09-18 22:00:32.554 UTC [34] ERROR:&nbsp; database &quot;prisma&quot; already existspostgres_1&nbsp; | 2018-09-18 22:00:32.554 UTC [34] STATEMENT:&nbsp; CREATE DATABASE &quot;prisma&quot;emerald-client exited with code 1emerald-server exited with code 1prisma_1&nbsp; &nbsp; | Obtaining exclusive agent lock...prisma_1&nbsp; &nbsp; | Obtaining exclusive agent lock... Successful.prisma_1&nbsp; &nbsp; | Deployment worker initialization complete.postgres_1&nbsp; | 2018-09-18 22:00:33.605 UTC [33] ERROR:&nbsp; null value in column &quot;lastPinged&quot; violates not-null constraintpostgres_1&nbsp; | 2018-09-18 22:00:33.605 UTC [33] DETAIL:&nbsp; Failing row contains (2d4cea92-4c6c-4c06-80a5-6632fd665a63, null).postgres_1&nbsp; | 2018-09-18 22:00:33.605 UTC [33] STATEMENT:&nbsp; insert into &quot;TelemetryInfo&quot; (&quot;id&quot;,&quot;lastPinged&quot;)&nbsp; values ($1,$2)prisma_1&nbsp; &nbsp; | Initializing workers...prisma_1&nbsp; &nbsp; | Successfully started 1 workers.emerald-client | yarn run v1.9.4emerald-client | error Command &quot;start&quot; not found.emerald-client | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.emerald-client | yarn run v1.9.4emerald-client | error Command &quot;start&quot; not found.emerald-client | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.emerald-server | yarn run v1.9.4emerald-server | $ /usr/app/server/node_modules/.bin/prisma deployemerald-server | /bin/sh: /usr/app/server/node_modules/.bin/prisma: not foundemerald-server | error Command failed with exit code 127.emerald-server | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.emerald-server | yarn run v1.9.4emerald-server | $ /usr/app/server/node_modules/.bin/prisma deployemerald-server | /bin/sh: /usr/app/server/node_modules/.bin/prisma: not foundemerald-server | error Command failed with exit code 127.emerald-server | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.prisma_1&nbsp; &nbsp; | Server running on :4466emerald-server | yarn run v1.9.4emerald-client | yarn run v1.9.4emerald-server | $ /usr/app/server/node_modules/.bin/prisma deployemerald-server | /bin/sh: /usr/app/server/node_modules/.bin/prisma: not foundemerald-server | error Command failed with exit code 127.emerald-server | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.emerald-client | error Command &quot;start&quot; not found.emerald-client | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.prisma_1&nbsp; &nbsp; | Version is up to date.[/CODE][/SPOILER]So my question is, what would be the best approach to resolve what I'm trying to accomplish?I did find this <a href="https://stackoverflow.com/questions/51178504/docker-compose-file-with-yarn-monorepo" target="_blank">https://stackoverflow.com/questions/51178504/docker-compose-file-with-yarn-monorepo</a> but doesn't seem like the most convenient solution (which didn't work either)</blockquote>

[QUOTE="MayoMayn, post: 438886, member: 71840"] So currently I have a mono repository that consists of the structure: [CODE] +-- project | +-- client | +-- assets | +-- src | +-- ... | +-- package.json | +-- angular.json | +-- tsconfig.json | +-- Dockerfile | +-- ... | +-- server | +-- database | +-- ... | +-- src | +-- ... | +-- package.json | +-- .graphqlconfig.yml | +-- tsconfig.json | +-- tsconfig.build.json | +-- Dockerfile | +-- ... +-- yarn.lock +-- package.json +-- lerna.json +-- tsconfig.json +-- tsconfig.base.json +-- docker-compose.yml [/CODE] And the problem is, that the docker-compose services commands can't figure out the workdirs of the images, so it tries to run the script commands in the root directory of the project. Tried to do switch out the bash command with [B]ls[/B] and it was still in the root directory of the project. [B]project/server/Dockerfile[/B] [SPOILER] [CODE] FROM node:alpine ARG NODE_ENV=development ENV NODE_ENV=${NODE_ENV} WORKDIR /usr/app/server COPY ./package.json . # COPY ../../yarn.lock . RUN yarn COPY . . EXPOSE 4242 [/CODE] [/SPOILER] [B]project/client/Dockerfile[/B] [SPOILER] [CODE] FROM node:alpine ARG NODE_ENV=development ENV NODE_ENV=${NODE_ENV} WORKDIR /usr/app/client COPY ./package.json . # COPY ../../yarn.lock . RUN yarn COPY . . EXPOSE 8080 [/CODE] [/SPOILER] [B]docker-compose.yml[/B] [SPOILER] [CODE] version: '3' volumes: postgres: services: prisma: image: prismagraphql/prisma:1.16 restart: always ports: - '4466:4466' environment: PRISMA_CONFIG: | port: 4466 databases: default: connector: postgres host: postgres port: 5432 user: prisma password: prisma migrations: true postgres: image: postgres:10.5 restart: always environment: POSTGRES_USER: prisma POSTGRES_PASSWORD: prisma volumes: - postgres:/var/lib/postgresql/data client: container_name: emerald-client command: yarn start restart: unless-stopped image: client build: context: ./project/client dockerfile: Dockerfile args: - NODE_ENV=development ports: - '3030:3030' volumes: - .:/usr/app/client server: container_name: emerald-server command: [sh, -c, 'yarn run prisma deploy && yarn start:dev'] restart: unless-stopped image: server depends_on: - prisma - postgres build: context: ./project/server dockerfile: Dockerfile args: - NODE_ENV=development ports: - '4242:4242' volumes: - .:/usr/app/server [/CODE] [/SPOILER] [B]Error log[/B] [SPOILER] [CODE] marcus-sa@DESKTOP-FUHH564:/e/Git/nest-prisma-angular-docker$ docker-compose up --build --remove-orphans Building client Step 1/9 : FROM node:alpine ---> 5ffbcf1d9932 Step 2/9 : ARG NODE_ENV=development ---> Running in 0fa11a29b762 Removing intermediate container 0fa11a29b762 ---> a943a9eaa495 Step 3/9 : ENV NODE_ENV=${NODE_ENV} ---> Running in 95e18bc28566 Removing intermediate container 95e18bc28566 ---> 349ada5022a1 Step 4/9 : WORKDIR /usr/app/client ---> Running in be4b60c56e33 Removing intermediate container be4b60c56e33 ---> ad0c66dbfb9d Step 5/9 : COPY ./package.json . ---> 4db7715d4607 Step 6/9 : RUN yarn ---> Running in 5c04efc3e1ad yarn install v1.9.4 warning package.json: No license field info No lockfile found. warning @npa/client@0.0.1: No license field [1/4] Resolving packages... [2/4] Fetching packages... (node:1) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead. info fsevents@1.2.4: The platform "linux" is incompatible with this module. info "fsevents@1.2.4" is an optional dependency and failed compatibility check. Excluding it from installation. [3/4] Linking dependencies... warning "@angular-devkit/build-angular > @ngtools/webpack@6.2.2" has unmet peer dependency "typescript@~2.4.0 || ~2.5.0 || ~2.6.0 || ~2.7.0 || ~2.8.0 || ~2.9.0". warning " > @angular/compiler-cli@6.1.7" has unmet peer dependency "typescript@>=2.7.2 <2.10". warning "@angular/compiler-cli > tsickle@0.32.1" has unmet peer dependency "typescript@>=2.4.2 <2.10". warning " > apollo-angular@1.3.0" has unmet peer dependency "apollo-link@^1.0.0". warning " > apollo-angular-link-http@1.2.0" has unmet peer dependency "apollo-link@^1.0.0". warning " > apollo-angular-link-http@1.2.0" has unmet peer dependency "graphql@^0.11.3 || ^0.12.3 || ^0.13.0". warning "apollo-angular-link-http > apollo-angular-link-http-common@1.2.0" has unmet peer dependency "apollo-link@^1.0.0". warning "apollo-angular-link-http > apollo-angular-link-http-common@1.2.0" has unmet peer dependency "graphql@^0.11.3 || ^0.12.3 || ^0.13.0". warning " > apollo-cache-inmemory@1.2.10" has unmet peer dependency "graphql@0.11.7 || ^0.12.0 || ^0.13.0". warning " > apollo-client@2.4.2" has unmet peer dependency "graphql@^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0". warning "apollo-client > apollo-link@1.2.3" has unmet peer dependency "graphql@^0.11.3 || ^0.12.3 || ^0.13.0 || ^14.0.0". [4/4] Building fresh packages... success Saved lockfile. Done in 39.46s. Removing intermediate container 5c04efc3e1ad ---> 1390d02cb152 Step 7/9 : COPY . . ---> 66ce4136a1c7 Step 8/9 : EXPOSE 8080 ---> Running in c308b6ef13fa Removing intermediate container c308b6ef13fa ---> 288e619440e4 Step 9/9 : RUN set -ex; if ["$NODE_ENV" = "production"]; then yarn build:prod fi; ---> Running in 3211c43f09c6 /bin/sh: syntax error: unexpected end of file (expecting "fi") ERROR: Service 'client' failed to build: The command '/bin/sh -c set -ex; if ["$NODE_ENV" = "production"]; then yarn build:prod fi;' returned a non-zero code: 2 marcus-sa@DESKTOP-FUHH564:/e/Git/nest-prisma-angular-docker$ docker-compose up --build --remove-orphans Building client Step 1/9 : FROM node:alpine ---> 5ffbcf1d9932 Step 2/9 : ARG NODE_ENV=development ---> Using cache ---> a943a9eaa495 Step 3/9 : ENV NODE_ENV=${NODE_ENV} ---> Using cache ---> 349ada5022a1 Step 4/9 : WORKDIR /usr/app/client ---> Using cache ---> ad0c66dbfb9d Step 5/9 : COPY ./package.json . ---> Using cache ---> 4db7715d4607 Step 6/9 : RUN yarn ---> Using cache ---> 1390d02cb152 Step 7/9 : COPY . . ---> bfdd009dc792 Step 8/9 : EXPOSE 8080 ---> Running in b50726163591 Removing intermediate container b50726163591 ---> 78fa6f2af004 Step 9/9 : RUN set -ex; if ["$NODE_ENV" = "production"]; then yarn build:prod; fi; ---> Running in 54b5e0bea7e3 + '[development' '=' production] /bin/sh: [development: not found Removing intermediate container 54b5e0bea7e3 ---> 9a3b15ea99b3 Successfully built 9a3b15ea99b3 Successfully tagged client:latest Building server Step 1/9 : FROM node:alpine ---> 5ffbcf1d9932 Step 2/9 : ARG NODE_ENV=development ---> Using cache ---> a943a9eaa495 Step 3/9 : ENV NODE_ENV=${NODE_ENV} ---> Using cache ---> 349ada5022a1 Step 4/9 : WORKDIR /usr/app/server ---> Running in 97c12e798c88 Removing intermediate container 97c12e798c88 ---> b9d853e03877 Step 5/9 : COPY ./package.json . ---> e9ce8755780b Step 6/9 : RUN yarn ---> Running in ba56cf48b5a8 yarn install v1.9.4 warning package.json: No license field info No lockfile found. warning @npa/server@0.0.1: No license field [1/4] Resolving packages... [2/4] Fetching packages... (node:1) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead. info fsevents@1.2.4: The platform "linux" is incompatible with this module. info "fsevents@1.2.4" is an optional dependency and failed compatibility check. Excluding it from installation. [3/4] Linking dependencies... warning "@nestjs/graphql > merge-graphql-schemas@1.5.4" has incorrect peer dependency "graphql@^0.11.7 || ^0.13.0". warning " > graphql-tools@3.1.1" has incorrect peer dependency "graphql@^0.13.0". warning "apollo-server-express > graphql-subscriptions@0.5.8" has incorrect peer dependency "graphql@^0.10.5 || ^0.11.3 || ^0.12.0 || ^0.13.0". warning "apollo-server-express > apollo-server-core > graphql-tag@2.9.2" has incorrect peer dependency "graphql@^0.9.0 || ^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0". warning "apollo-server-express > @apollographql/apollo-upload-server@5.0.3" has incorrect peer dependency "graphql@^0.13.1". warning "prisma > prisma-cli-core@1.0.79" has incorrect peer dependency "graphql@^0.12.0 || ^0.13.0". warning " > prisma-binding@2.1.5" has incorrect peer dependency "graphql@^0.11.0 || ^0.12.0 || ^0.13.0". warning "prisma-binding > apollo-link@1.2.2" has incorrect peer dependency "graphql@^0.11.3 || ^0.12.3 || ^0.13.0". warning "prisma-binding > graphql-import@0.5.2" has incorrect peer dependency "graphql@^0.11.0 || ^0.12.0 || ^0.13.0". warning "prisma-binding > graphql-tools@3.1.0" has incorrect peer dependency "graphql@^0.13.0". warning "prisma-binding > subscriptions-transport-ws@0.9.8" has incorrect peer dependency "graphql@^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.1". warning "prisma-binding > graphql-binding@2.2.4" has incorrect peer dependency "graphql@^0.11.0 || ^0.12.0 || ^0.13.0". warning "prisma-binding > graphql-binding > graphql-import@0.5.3" has incorrect peer dependency "graphql@^0.11.0 || ^0.12.0 || ^0.13.0". [4/4] Building fresh packages... success Saved lockfile. Done in 36.16s. Removing intermediate container ba56cf48b5a8 ---> 6da36da96c51 Step 7/9 : COPY . . ---> 5cbf9f43aaf3 Step 8/9 : EXPOSE 4242 ---> Running in 3b724af3f3a4 Removing intermediate container 3b724af3f3a4 ---> dc2f82318399 Step 9/9 : RUN set -ex; if ["$NODE_ENV" = "production"]; then yarn build; fi; ---> Running in 7d318d723049 + '[development' '=' production] /bin/sh: [development: not found Removing intermediate container 7d318d723049 ---> a37ec2260c27 Successfully built a37ec2260c27 Successfully tagged server:latest Starting nest-prisma-angular-docker_prisma_1 ... done Recreating nest-prisma-angular-docker_client_1 ... done Starting nest-prisma-angular-docker_postgres_1 ... done Recreating nest-prisma-angular-docker_server_1 ... done Attaching to nest-prisma-angular-docker_prisma_1, nest-prisma-angular-docker_postgres_1, emerald-client, emerald-server postgres_1 | 2018-09-18 22:00:27.700 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432 postgres_1 | 2018-09-18 22:00:27.700 UTC [1] LOG: listening on IPv6 address "::", port 5432 emerald-client | yarn run v1.9.4 emerald-server | yarn run v1.9.4 postgres_1 | 2018-09-18 22:00:27.738 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" postgres_1 | 2018-09-18 22:00:27.786 UTC [26] LOG: database system was interrupted; last known up at 2018-09-18 21:50:54 UTC emerald-client | error Command "start" not found. emerald-client | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. emerald-server | $ /usr/app/server/node_modules/.bin/prisma deploy emerald-server | /bin/sh: /usr/app/server/node_modules/.bin/prisma: not found emerald-server | error Command failed with exit code 127. emerald-server | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. postgres_1 | 2018-09-18 22:00:28.911 UTC [26] LOG: database system was not properly shut down; automatic recovery in progress postgres_1 | 2018-09-18 22:00:28.924 UTC [26] LOG: invalid record length at 0/1677BC0: wanted 24, got 0 postgres_1 | 2018-09-18 22:00:28.924 UTC [26] LOG: redo is not required postgres_1 | 2018-09-18 22:00:29.040 UTC [1] LOG: database system is ready to accept connections postgres_1 | 2018-09-18 22:00:32.554 UTC [34] ERROR: database "prisma" already exists postgres_1 | 2018-09-18 22:00:32.554 UTC [34] STATEMENT: CREATE DATABASE "prisma" emerald-client exited with code 1 emerald-server exited with code 1 prisma_1 | Obtaining exclusive agent lock... prisma_1 | Obtaining exclusive agent lock... Successful. prisma_1 | Deployment worker initialization complete. postgres_1 | 2018-09-18 22:00:33.605 UTC [33] ERROR: null value in column "lastPinged" violates not-null constraint postgres_1 | 2018-09-18 22:00:33.605 UTC [33] DETAIL: Failing row contains (2d4cea92-4c6c-4c06-80a5-6632fd665a63, null). postgres_1 | 2018-09-18 22:00:33.605 UTC [33] STATEMENT: insert into "TelemetryInfo" ("id","lastPinged") values ($1,$2) prisma_1 | Initializing workers... prisma_1 | Successfully started 1 workers. emerald-client | yarn run v1.9.4 emerald-client | error Command "start" not found. emerald-client | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. emerald-client | yarn run v1.9.4 emerald-client | error Command "start" not found. emerald-client | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. emerald-server | yarn run v1.9.4 emerald-server | $ /usr/app/server/node_modules/.bin/prisma deploy emerald-server | /bin/sh: /usr/app/server/node_modules/.bin/prisma: not found emerald-server | error Command failed with exit code 127. emerald-server | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. emerald-server | yarn run v1.9.4 emerald-server | $ /usr/app/server/node_modules/.bin/prisma deploy emerald-server | /bin/sh: /usr/app/server/node_modules/.bin/prisma: not found emerald-server | error Command failed with exit code 127. emerald-server | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. prisma_1 | Server running on :4466 emerald-server | yarn run v1.9.4 emerald-client | yarn run v1.9.4 emerald-server | $ /usr/app/server/node_modules/.bin/prisma deploy emerald-server | /bin/sh: /usr/app/server/node_modules/.bin/prisma: not found emerald-server | error Command failed with exit code 127. emerald-server | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. emerald-client | error Command "start" not found. emerald-client | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. prisma_1 | Version is up to date. [/CODE] [/SPOILER] So my question is, what would be the best approach to resolve what I'm trying to accomplish? I did find this [URL]https://stackoverflow.com/questions/51178504/docker-compose-file-with-yarn-monorepo[/URL] but doesn't seem like the most convenient solution (which didn't work either) [/QUOTE]

Verification

Reply to thread

Connect with us

Newest members