search

calcom / docker

The Docker configuration for Cal.com is an effort powered by people within the community. Cal.com, Inc. does not provide official support for Docker, but we will accept fixes and documentation. Use at your own risk.
MIT License
662 stars 344 forks source link

Building calcom image fails with exit code 129 not sure of cause #233

Closed kvnam closed 1 year ago

kvnam commented 1 year ago

Hey, I recently upgraded my calcom submodule with the latest calcom branch and also update the Dockerfile with the latest in this repo. I was able to build the image with previous version successfully, but now when I try to run docker compose build I get this error

... many similar lines for deps
#0 99.00 ➤ YN0013: │ object.entries@npm:1.1.6 can't be found in the cache and will be fetched from the remote registry
#0 99.00 ➤ YN0013: │ object.fromentries@npm:2.0.5 can't be found in the cache and will be fetched from the remote
#0 99.00 [output clipped, log limit 1MiB reached]
#0 284.1  WARNING  cannot find a .git folder. Falling back to manual file hashing (which may be slower). If you are running this build in a pruned directory, you can ignore this message. Otherwise, please initialize a git repository in the root of your monorepo
------
failed to solve: executor failed running [/bin/sh -c yarn config set httpTimeout 1200000 &&     npx turbo prune --scope=@calcom/web --docker &&     yarn install &&     yarn db-deploy &&     yarn --cwd packages/prisma seed-app-store]: exit code: 129

I'm using an external database so DATABASE_URL has been correctly set. I can't tell what is causing this error, so not sure if that is related. I have run yarn db-deploy locally on my database successfully before, so this command should not fail.

I have no idea what is causing this error so can't even look into fixing this. It would be awesome if someone can point me in the right direction here to either resolve this, or debug this error better. 🙏

EDIT: So the issue is that yarn install is failing. This step is failing in both the Docker container and the Vercel deployments.

Vercel deployment error logs


➤ YN0002: │ storybook-addon-next@npm:1.6.9 [b9453] doesn't provide webpack (p0771c), requested by postcss-loader
--
07:31:43.898 | ➤ YN0002: │ storybook-addon-next@npm:1.6.9 [b9453] doesn't provide webpack (p6906d), requested by sass-loader
07:31:43.898 | ➤ YN0000: │ Some peer dependencies are incorrectly met; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code
07:31:43.904 | ➤ YN0000: └ Completed in 0s 987ms
07:31:44.162 | ➤ YN0000: ┌ Post-resolution validation
07:31:44.163 | ➤ YN0028: │ The lockfile would have been modified by this install, which is explicitly forbidden.
07:31:44.163 | ➤ YN0000: └ Completed in 0s 273ms
07:31:44.164 | ➤ YN0000: Failed with errors in 1s 266ms
07:31:44.241 | Error: Command "yarn install" exited with 1
07:31:44.555 | BUILD_UTILS_SPAWN_1: Command "yarn install" exited with 1
emrysal commented 1 year ago

Hey @kvnam this should be fixed in the latest release - there was a broken yarn lockfile