eclipse-emfcloud/coffee-editor

Docker build fails on frontend

dmm9 opened this issue · 2 comments

dmm9 commented

The docker build fails in the frontend build step.

Output:

...
132.4 coffee-welcome-page: yarn run v1.22.19
132.5 coffee-welcome-page: $ yarn run clean && yarn run build && yarn lint
133.0 coffee-welcome-page: $ rimraf tsconfig.tsbuildinfo lib
133.5 coffee-welcome-page: $ tsc
136.5 coffee-editor-extension: Done in 29.19s.
137.7 coffee-workflow-glsp: $ eslint -c ../.eslintrc.js --ext .ts,.tsx ./src
138.6 coffee-workflow-analyzer: $ eslint -c ../.eslintrc.js --ext .ts,.tsx ./src
141.5 coffee-welcome-page: src/browser/welcome-page-widget.tsx(23,33): error TS2307: Cannot find module 'coffee-workflow-analyzer/lib/browser/command-contribution' or its corresponding type declarations.
141.5 coffee-welcome-page: error Command failed with exit code 2.
141.5 coffee-welcome-page: info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
141.5 coffee-welcome-page: error Command failed with exit code 2.
141.5 coffee-welcome-page: info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
141.5 lerna ERR! yarn run prepare exited 2 in 'coffee-welcome-page'
141.6 lerna WARN complete Waiting for 2 child processes to exit. CTRL-C to exit immediately.
141.6 error Command failed with exit code 2.
141.6 info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
------
Dockerfile:38
--------------------
  37 |
  38 | >>> RUN yarn install && \
  39 | >>>     yarn production
  40 |
--------------------
ERROR: failed to solve: process "/bin/sh -c yarn install &&     yarn production" did not complete successfully: exit code: 2

Version coffee-editor:

Environment:

  • Ubuntu 22.04.2 LTS (Win10+WSL)
  • Docker Engine v24.0.5

Command:

clone ... && cd coffee-editor
sudo docker build -t "coffee-editor:latest" .
dmm9 commented

Adding missing dependencies in package.json of coffee.welcome-page solves the issue and the docker build completes successfully. I have crated a pull request: #518

Fixed by #518