Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Calcom Docker update from version 4.5 not possible #390

Open
techsupportkoeln opened this issue Nov 6, 2024 · 3 comments
Open

Calcom Docker update from version 4.5 not possible #390

techsupportkoeln opened this issue Nov 6, 2024 · 3 comments

Comments

@techsupportkoeln
Copy link

i have 2 Calcom Docker Container with the version 4.5 running. If i try to update to a newer version, calcom is not accessible anymore. I got for one second an 500 error and than a blank screen.

docker ps shows the following:

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
058bd3530d97 calcom.docker.scarf.sh/calcom/cal.com "docker-entrypoint.s…" 4 minutes ago Up 4 minutes (unhealthy) 0.0.0.0:3000->3000/tcp, :::3000->3000/tcp calcom_calcom_1
03c9bae547bd postgres "docker-entrypoint.s…" 4 minutes ago Restarting (1) 29 seconds ago

is there any changes i have to made to update to a newer version as 4.5?

@techsupportkoeln
Copy link
Author

i think it is a problem with the database version.

I changed in the docker-compose.yml file the following line:

  • database-data:/var/lib/postgresql/data/

to:

  • database-data:/var/lib/postgresql@16/data/

and then calcom starts with a fresh environment. But i loose all my configuration so this is no option.

@techsupportkoeln
Copy link
Author

database |
database | PostgreSQL Database directory appears to contain a database; Skipping initialization
database |
database | 2024-11-06 09:28:02.077 UTC [1] FATAL: database files are incompatible with server
database | 2024-11-06 09:28:02.077 UTC [1] DETAIL: The data directory was initialized by PostgreSQL version 16, which is not compatible with this version 17.0 (Debian 17.0-1.pgdg120+1).

@Speedy059
Copy link

I just ran into this as well. Is there any update on this? How do we upgrade without breaking the PostgreSQL?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants