Skip to content

[Bug]: dependency failed to start: container planka-postgres-1 is unhealthy #1164

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

Open
moritzmofi opened this issue May 30, 2025 · 3 comments

Comments

@moritzmofi
Copy link

Where is the problem occurring?

None

What browsers are you seeing the problem on?

No response

Current behavior

I try to install planka v2 with a docker-compose
I cannot start the docker-compose with up -d
Error:
dependency failed to start: container planka-postgres-1 is unhealthy

what can I do?

Desired behavior

No response

Steps to reproduce

Install with docker-compose
Error:
dependency failed to start: container planka-postgres-1 is unhealthy

Other information

No response

@meltyshev
Copy link
Member

Hi! It's difficult to say what might be wrong without seeing the logs or knowing more about your environment and installation method. You can try retrieving the logs by running docker logs planka-postgres-1.

@moritzmofi
Copy link
Author

moritzmofi commented Jun 6, 2025

Hi! It's difficult to say what might be wrong without seeing the logs or knowing more about your environment and installation method. You can try retrieving the logs by running docker logs planka-postgres-1.

here are the logs:
✘ Container planka-postgres-1 Error 0.8s
dependency failed to start: container planka-postgres-1 is unhealthy
root@docker:~/planka# docker logs planka-postgres-1

PostgreSQL Database directory appears to contain a database; Skipping initialization

2025-06-06 14:24:41.494 UTC [1] FATAL: database files are incompatible with server
2025-06-06 14:24:41.494 UTC [1] DETAIL: The data directory was initialized by PostgreSQL version 14, which is not compatible with this version 16.9.

@meltyshev
Copy link
Member

Ah, that makes sense. Your PostgreSQL version has changed, and the previous data isn't compatible with the new version. You'll need to back up the existing data and restore it into the new version.

Here are some links that might help:
#949 (comment)
https://www.cloudytuts.com/tutorials/docker/how-to-upgrade-postgresql-in-docker-and-kubernetes/

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