Coolify & Immich Upgrade
Hi! I updated immich to the latest version changing the docker_compose.yml in coolify like told in the upgrade notifications. now, my database container keeps showing as unhealthy. immich is running, showing pictures and so on etc. it looks strange. here my docker compose file:
services:
immich:
image: 'ghcr.io/immich-app/immich-server:release'
volumes:
- 'immich-uploads:/usr/src/app/upload'
- '/etc/localtime:/etc/localtime:ro'
environment:
- SERVICE_FQDN_IMMICH_2283
- UPLOAD_LOCATION=./library
- DB_DATA_LOCATION=./postgres
- DB_PASSWORD=$SERVICE_PASSWORD_POSTGRES
- DB_USERNAME=$SERVICE_USER_POSTGRES
- 'DB_DATABASE_NAME=${DB_DATABASE_NAME:-immich}'
- 'TZ=${TZ:-Etc/UTC}'
depends_on:
redis:
condition: service_healthy
database:
condition: service_healthy
healthcheck:
disable: false
immich-machine-learning:
container_name: immich_machine_learning
image: 'ghcr.io/immich-app/immich-machine-learning:release'
volumes:
- 'immich-model-cache:/cache'
environment:
- UPLOAD_LOCATION=./library
- DB_DATA_LOCATION=./postgres
- DB_PASSWORD=$SERVICE_PASSWORD_POSTGRES
- DB_USERNAME=$SERVICE_USER_POSTGRES
- 'DB_DATABASE_NAME=${DB_DATABASE_NAME:-immich}'
- 'TZ=${TZ:-Etc/UTC}'
healthcheck:
disable: false
redis:
image: 'redis:7.4-alpine'
healthcheck:
test:
- CMD
- redis-cli
- PING
interval: 5s
timeout: 10s
retries: 20
database:
image: ghcr.io/immich-app/postgres:14-vectorchord0.3.0-pgvectors0.2.0
environment:
POSTGRES_PASSWORD: '${SERVICE_PASSWORD_POSTGRES}'
POSTGRES_USER: '${SERVICE_USER_POSTGRES}'
POSTGRES_DB: '${DB_DATABASE_NAME:-immich}'
POSTGRES_INITDB_ARGS: '--data-checksums'
volumes:
- 'immich-postgres-data:/var/lib/postgresql/data'
restart: always
How do I make database container show healthy again
4 Replies
:wave: Hey @freaky,
Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich :immich:.
References
- Container Logs:
docker compose logs docs
- Container Status: docker ps -a docs
- Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
- Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA
Checklist
I have...
1. :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
2. :ballot_box_with_check: read applicable release notes.
3. :blue_square: reviewed the FAQs for known issues.
4. :blue_square: reviewed Github for known issues.
5. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy).
6. :blue_square: uploaded the relevant information (see below).
7. :blue_square: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable
(an item can be marked as "complete" by reacting with the appropriate number)
Information
In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider:
- Your docker-compose.yml and .env files.
- Logs from all the containers and their status (see above).
- All the troubleshooting steps you've tried so far.
- Any recent changes you've made to Immich or your system.
- Details about your system (both software/OS and hardware).
- Details about your storage (filesystems, type of disks, output of commands like fdisk -l and df -h).
- The version of the Immich server, mobile app, and other relevant pieces.
- Any other information that you think might be relevant.
Please paste files and logs with proper code formatting, and especially avoid blurry screenshots.
Without the right information we can't work out what the problem is. Help us help you ;)
If this ticket can be closed you can use the /close command, and re-open it later if needed.I guess it's because the database healthcheck has been removed. There was previously one, and it is removed, as showed in the release post.
However, I think coolify rely on theses healthcheck to show the container status.
Would be nice to have a new healthcheck provided I guess :)
The health check is part of the container itself now.
Oh nice thank you !
But do you know how can I write it in the docker compose so coolify can check if it pass or not ?