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
646 stars 338 forks source link

yarn error when running latest version #282

Closed imchairmanm closed 11 months ago

imchairmanm commented 11 months ago

Hello. On the latest version published to Docker Hub, I'm getting a yarn error similar to the one described here. Previous versions of the image work as expected.

The specific output looks like this on the systems I've tested:

Internal Error: @calcom/make@workspace:packages/app-store/make: This package doesn't seem to be present in your lockfile; run "yarn install" to update the lockfile
    at P0.getCandidates (/calcom/.yarn/releases/yarn-3.4.1.cjs:435:5145)
    at yf.getCandidates (/calcom/.yarn/releases/yarn-3.4.1.cjs:391:1264)
    at /calcom/.yarn/releases/yarn-3.4.1.cjs:439:7693
    at of (/calcom/.yarn/releases/yarn-3.4.1.cjs:390:11070)
    at ge (/calcom/.yarn/releases/yarn-3.4.1.cjs:439:7673)
    at async Promise.allSettled (index 31)
    at async $s (/calcom/.yarn/releases/yarn-3.4.1.cjs:390:10398)
    at async /calcom/.yarn/releases/yarn-3.4.1.cjs:439:8205
    at async ti.startProgressPromise (/calcom/.yarn/releases/yarn-3.4.1.cjs:390:47579)
    at async je.resolveEverything (/calcom/.yarn/releases/yarn-3.4.1.cjs:439:6233)

Do the image need to be rebuilt or is there something I should do on my end? Thanks!

jdreinhardt commented 11 months ago

I had the same issue, but everything worked when I downgraded to the previous release v3.2.7.1. You can use the instructions in #274 but use v3.2.7.1 instead of v3.1.0 and it should work.

imchairmanm commented 11 months ago

Thanks for the confirmation. Yes, I'm using the previous version right now. Hoping to not have to pin to that version though if possible.

aukfood commented 11 months ago

Same problem and downgrade do v3.2.7.1 works

imchairmanm commented 11 months ago

The newest image seems to deploy without an issue :+1:

Thanks for the quick fix!

aukfood commented 11 months ago

I confirm that works with version 3.2.9