Issue with docker hub images

buzzard10 commented 5 months ago

Hello Guys, i don't know why but last tag on docker hub is 3.7.16. The newest release on github is 3.8.0-rc

https://hub.docker.com/r/calcom/cal.com/tags

keithwillcode commented 5 months ago

@buzzard10 hey sorry for the issues. We are actively looking at why these are failing.

mariushosting commented 5 months ago

@keithwillcode The latest calcom docker version has stopped working, The most recent Calcom Docker version that works is version 3.7.11 and any version under 3.7.11

Version 3.7.15, 3.7.16 gives the following error message:

yarn start • Packages in scope: @calcom/web • Running start in 1 packages • Remote caching disabled @calcom/web:start: cache bypass, force executing b0182874aa91d7f3 @calcom/web:start: Duplicate value found in common.json keys: seats_available_other and seats_available_one @calcom/web:start: Duplicate value found in common.json keys: location_variable and location @calcom/web:start: Duplicate value found in common.json keys: additional_notes_variable and additional_notes @calcom/web:start: Duplicate value found in common.json keys: already_have_account and already_have_an_account @calcom/web:start: Duplicate value found in common.json keys: timezone_variable and timezone @calcom/web:start: Duplicate value found in common.json keys: scheduling_for_your_team and workflow_automation @calcom/web:start: Duplicate value found in common.json keys: saml_sso and saml_config @calcom/web:start: Duplicate value found in common.json keys: advanced_managed_events_description and unified_billing_description @calcom/web:start: ▲ Next.js 13.5.5 @calcom/web:start: - Local: http://localhost:3000 @calcom/web:start: @calcom/web:start: ✓ Ready in 1283ms @calcom/web:start: 00:54:26:588 ERROR[redactError] Error: {"name":"PrismaClientKnownRequestError","code":"P2021","clientVersion":"5.4.2","meta":{"table":"public.Feature"}} @calcom/web:start: PrismaClientKnownRequestError: @calcom/web:start: Invalid prisma.user.count() invocation: @calcom/web:start: @calcom/web:start: @calcom/web:start: The table public.users does not exist in the current database. @calcom/web:start: at Cn.handleRequestError (/calcom/node_modules/@prisma/client/runtime/library.js:123:6817) @calcom/web:start: at Cn.handleAndLogRequestError (/calcom/node_modules/@prisma/client/runtime/library.js:123:6206) @calcom/web:start: at Cn.request (/calcom/node_modules/@prisma/client/runtime/library.js:123:5926) @calcom/web:start: at async l (/calcom/node_modules/@prisma/client/runtime/library.js:128:9968) @calcom/web:start: at async getServerSideProps (/calcom/apps/web/.next/server/pages/auth/login.js:1:10204) { @calcom/web:start: code: 'P2021', @calcom/web:start: clientVersion: '5.4.2', @calcom/web:start: meta: { table: 'public.users' } @calcom/web:start: } @calcom/web:start: react-i18next:: You will need to pass in an i18next instance by using initReactI18next

buzzard10 commented 5 months ago

@mariushosting hello! I can confirm that i have similar issue. After i've upgrade to the newest available image, i can't log in because i have error 500.

And Mariushosting, thank you for your great work! I'm a fan of your blog ;)

mariushosting commented 5 months ago

@mariushosting hello! I can confirm that i have similar issue. After i've upgrade to the newest available image, i can't log in because i have error 500.

And Mariushosting, thank you for your great work! I'm a fan of your blog ;)

In the meantime change the image calcom/cal.com:latest with image: calcom/cal.com:v3.7.11

buzzard10 commented 5 months ago

@mariushosting i've already did that. Hope community will be able to figure out the problem and we'll be able to use it :)

mariushosting commented 5 months ago

@mariushosting i've already did that. Hope community will be able to figure out the problem and we'll be able to use it :)

Awesome! Just wait for @keithwillcode to look into this!

lejacobroy commented 4 months ago

I have the same problem on my end, I confirm that the v3.7.11 tag is working. Here's the anonymized logs if I start the v3.7.15 or newer builds:

calcom | Error: Prisma schema validation - (get-config wasm) calcom | Error code: P1012 calcom | error: Environment variable not found: DATABASE_DIRECT_URL. calcom | --> schema.prisma:7 calcom | | calcom | 6 | url = env("DATABASE_URL") calcom | 7 | directUrl = env("DATABASE_DIRECT_URL") calcom | | calcom | Validation Error Count: 1 calcom | [Context: getConfig] database | 2024-02-21 16:14:16.806 UTC [33] ERROR: column users.movedToProfileId does not exist at character 1281 calcom | Invalid prisma.user.findFirst() invocation: calcom | The column users.movedToProfileId does not exist in the current database. calcom | at Cn.handleRequestError (/calcom/node_modules/@prisma/client/runtime/library.js:123:6817) calcom | at Cn.handleAndLogRequestError (/calcom/node_modules/@prisma/client/runtime/library.js:123:6206) calcom | at Cn.request (/calcom/node_modules/@prisma/client/runtime/library.js:123:5926) calcom | at async l (/calcom/node_modules/@prisma/client/runtime/library.js:128:9968) calcom | at async seedAppData (/calcom/packages/prisma/seed-app-store.ts:31:19) calcom | at async main (/calcom/packages/prisma/seed-app-store.ts:384:3) { calcom | code: 'P2022', calcom | clientVersion: '5.4.2', calcom | meta: { column: 'users.movedToProfileId' } calcom | }

So it seems like the ENV variables changed and need to add 'DATABASE_DIRECT_URL'. In my .env file, I added an entry for this variable, with the same value as the older 'DATABASE_URL' variable. With that change, I can run the v3.7.15 tags up to the latest available (v3.7.16).

xcellentavi commented 4 months ago

So it seems like the ENV variables changed and need to add 'DATABASE_DIRECT_URL'. In my .env file, I added an entry for this variable, with the same value as the older 'DATABASE_URL' variable. With that change, I can run the v3.7.15 tags up to the latest available (v3.7.16).

Is that all that needs to be done to correct these errors? And we need both variables DATABASE_URL and DATABASE_DIRECT_URL?

MarioNoll commented 4 months ago

See https://github.com/calcom/docker/issues/323

Is that all that needs to be done to correct these errors? And we need both variables DATABASE_URL and DATABASE_DIRECT_URL?

Adding DATABASE_DIRECT_URL did not change anything for me.

NexusEFR commented 4 months ago

Working for me latest tags after adding env variable, in unraid server...thanks!

buzzard10 commented 4 months ago

Any updates regarding availability of newest versions on docker hub?

xcellentavi commented 4 months ago

Any updates regarding availability of newest versions on docker hub?

My container on unraid is running v.3.8.6-sh according to what I see at the bottom left corner of my settings page.

v3.8.6 is showing as the latest release on github: https://github.com/calcom/cal.com/releases

The repo on docker hub matches also: https://hub.docker.com/r/calcom/cal.com/tags

I was running 3.8.5-sh yesterday, but docker hub is only showing v3.7.16 as the previous tag, so not sure why it doesn't have anything in between.

NexusEFR commented 4 months ago

Wow, great! I did not know that you could see the version of the image docker on the page of the platform cal.com selfhosted..Attachment screen capture with the image .. and what I see still not in the last image updated, but comment higher between v3.7.11 and the last there were errors that did not let enter to log in until entering the variables of environment mentioned..