starred/planka
1
0
Fork 0
mirror of https://github.com/plankanban/planka.git synced 2026-07-16 05:53:57 +03:00
Code Issues 396 Packages Projects Releases 21 Wiki Activity

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

New Issue
Closed
opened 2026-02-04 21:05:19 +03:00 by OVERLORD · 4 comments
OVERLORD commented 2026-02-04 21:05:19 +03:00
Owner
Copy Link

Originally created by @moritzmofi on GitHub (May 30, 2025).

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

Originally created by @moritzmofi on GitHub (May 30, 2025). ### 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_
OVERLORD commented 2026-02-04 21:05:32 +03:00
Author
Owner
Copy Link

@meltyshev commented on GitHub (Jun 5, 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.

@meltyshev commented on GitHub (Jun 5, 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`.
OVERLORD commented 2026-02-04 21:05:38 +03:00
Author
Owner
Copy Link

@moritzmofi commented on GitHub (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.

@moritzmofi commented on GitHub (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.
OVERLORD commented 2026-02-04 21:05:44 +03:00
Author
Owner
Copy Link

@meltyshev commented on GitHub (Jun 6, 2025):

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:
https://github.com/plankanban/planka/issues/949#issuecomment-2659378566
https://www.cloudytuts.com/tutorials/docker/how-to-upgrade-postgresql-in-docker-and-kubernetes/

@meltyshev commented on GitHub (Jun 6, 2025): 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: https://github.com/plankanban/planka/issues/949#issuecomment-2659378566 https://www.cloudytuts.com/tutorials/docker/how-to-upgrade-postgresql-in-docker-and-kubernetes/
OVERLORD commented 2026-02-04 21:05:55 +03:00
Author
Owner
Copy Link

@moritzmofi commented on GitHub (Jun 7, 2025):

thanx -this helped me

@moritzmofi commented on GitHub (Jun 7, 2025): thanx -this helped me
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
documentation
documentation
duplicate
enhancement
good first issue
help wanted
pull-request
Mirrored from GitHub Pull Request
 question
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/planka#721
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?