Immich upgrade to 1.133 on portsiner synology nas. No such DB error
Hello.
Im updating the immich instance from portainer on my synology nas by the stack file.
I altered my code for the db to following:
immich-db:
image: ghcr.io/immich-app/postgres:14-vectorchord0.3.0-pgvectors0.2.0
container_name: Immich-DB
hostname: immich-db
security_opt:
- no-new-privileges:true
volumes:
- /volume1/docker/immich/db:/var/lib/postgresql/data:rw
environment:
- TZ=Europe/Amsterdam
- POSTGRES_DB=immich
- POSTGRES_USER=xxxx
- POSTGRES_PASSWORD=xxxx
- DB_STORAGE_TYPE=HDD
restart: on-failure:5
Updated the stack, containers start up, but the DB container fails according to docker with the following error: Container {"message": "No such container: 8e456ff1c03b_Immich-DB") bestaat niet.
The container name somehow renamed itself from Immich-DB to 8e456ff1c03b_Immich-DB"
Please help 😢
16 Replies
:wave: Hey @Shaquille_Oatmeal,
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. :blue_square: verified I'm on the latest release(note that mobile app releases may take some time).
2. :blue_square: 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.services:
immich-redis:
image: redis
container_name: Immich-REDIS
hostname: immich-redis
security_opt:
- no-new-privileges:true
healthcheck:
test: ["CMD-SHELL", "redis-cli ping exit 1"]
user: 1026:100
environment:
- TZ=Europe/Amsterdam
volumes:
- /volume1/docker/immich/redis:/data:rw
restart: on-failure:5
immich-db:
image: ghcr.io/immich-app/postgres:14-vectorchord0.3.0-pgvectors0.2.0
container_name: Immich-DB
hostname: immich-db
security_opt:
- no-new-privileges:true
volumes:
- /volume1/docker/immich/db:/var/lib/postgresql/data:rw
environment:
- TZ=Europe/Amsterdam
- POSTGRES_DB=immich
- POSTGRES_USER=immichuser
- POSTGRES_PASSWORD=immichpw
- DB_STORAGE_TYPE=HDD
restart: on-failure:5
immich-server:
image: ghcr.io/immich-app/immich-server:release
container_name: Immich-SERVER
hostname: immich-server
user: 1026:100
security_opt:
- no-new-privileges:true
env_file:
- stack.env
ports:
- 8212:2283
volumes:
- /volume1/docker/immich/upload:/usr/src/app/upload:rw
restart: on-failure:5
depends_on:
immich-redis:
condition: service_healthy
immich-db:
condition: service_started
immich-machine-learning:
image: ghcr.io/immich-app/immich-machine-learning:release
container_name: Immich-LEARNING
hostname: immich-machine-learning
user: 1026:100
security_opt:
- no-new-privileges:true
env_file:
- stack.env
volumes:
- /volume1/docker/immich/upload:/usr/src/app/upload:rw
- /volume1/docker/immich/cache:/cache:rw
- /volume1/docker/immich/matplotlib:/matplotlib:rw
environment:
- MPLCONFIGDIR=/matplotlib
restart: on-failure:5
depends_on:
immich-db:
condition: service_started
Previous db image:
image: tensorchord/pgvecto-rs:pg16-v0.2.0
Previous stack compose:
services:
immich-redis:
image: redis
container_name: Immich-REDIS
hostname: immich-redis
security_opt:
- no-new-privileges:true
healthcheck:
test: ["CMD-SHELL", "redis-cli ping exit 1"]
user: 1026:100
environment:
- TZ=Europe/Amsterdam
volumes:
- /volume1/docker/immich/redis:/data:rw
restart: on-failure:5
immich-db:
image: tensorchord/pgvecto-rs:pg16-v0.2.0
container_name: Immich-DB
hostname: immich-db
security_opt:
- no-new-privileges:true
healthcheck:
test: ["CMD", "pg_isready", "-q", "-d", "immich", "-U", "immichuser"]
interval: 10s
timeout: 5s
retries: 5
volumes:
- /volume1/docker/immich/db:/var/lib/postgresql/data:rw
environment:
- TZ=Europe/Amsterdam
- POSTGRES_DB=immich
- POSTGRES_USER=immichuser
- POSTGRES_PASSWORD=immichpw
restart: on-failure:5
immich-server:
image: ghcr.io/immich-app/immich-server:release
container_name: Immich-SERVER
hostname: immich-server
user: 1026:100
security_opt:
- no-new-privileges:true
env_file:
- stack.env
ports:
- 8212:2283
volumes:
- /volume1/docker/immich/upload:/usr/src/app/upload:rw
restart: on-failure:5
depends_on:
immich-redis:
condition: service_healthy
immich-db:
condition: service_started
immich-machine-learning:
image: ghcr.io/immich-app/immich-machine-learning:release
container_name: Immich-LEARNING
hostname: immich-machine-learning
user: 1026:100
security_opt:
- no-new-privileges:true
I see all the immich containers are renamed and complaining about not existing
Env
Went from the latest version to 1.133
your new database image should be
ghcr.io/immich-app/postgres:16-vectorchord0.3.0-pgvectors0.2.0 instead of ghcr.io/immich-app/postgres:14-vectorchord0.3.0-pgvectors0.2.0 since you were using Postgresql version 16Will check now
DB is up now, only issue remains the renamed ML, Redis and Server
When I click these contsiners "no such container exists" message from docker
maybe stop the project and do rebuild ?
How to do this for portainer? The containers show up in docker but I have no active projects in docker
sorry, I thought you were running synology container manager
for portainer just stop the stack, go to editor, save and make sure to check pull new images. that will recreate the containers
No worried
Found a way in portainer to recreate the server, ml and redis like this:
Not to be done for the DB!!!
So after the postgress line change as suggested by @Alex for the DB container and recreating the ML, Redis and Server container via portainer, upgrade succesfull
Thanks!
This thread has been closed. To re-open, use the button below.