Update Immich in Portainer - Newest Version 1.36.0 - Path to my Share Folder NAS

[RadioHerzblut]

Hello – I have my Immich data on my NAS.

Immich runs on Portainer for me. The path to NAS is not in the EVN tab.
In Portainer under VOLUMES, I see the path to:

container = /usr/src/app/upload
host = /mnt/immich/uplods (this is the path to NAS).

Does anyone here have experience with what needs to be changed in Portainer?

I made a backup in Proxmox before the update.
After the UPDATE in Portainer, Immich was no longer accessible.

I restored the backup. I am back to the old version.

I would be grateful for any tips.

[alextran1502]

You don't need to change anything regarding the breaking changes as far as I see

[alextran1502]

If you can get the server log when it starts up, it will show you more information

Make sure to run docker compose pull then docker compose up for a proper update

[RadioHerzblut]

Hi Alex - I pull the Image and recreate the container with Portaier.

The output of the logsfile:

/bin/bash: start.sh: No such file or directory

/bin/bash: start.sh: No such file or directory

/bin/bash: start.sh: No such file or directory

/bin/bash: start.sh: No such file or directory

/bin/bash: start.sh: No such file or directory

/bin/bash: start.sh: No such file or directory

/bin/bash: start.sh: No such file or directory

/bin/bash: start.sh: No such file or directory

/bin/bash: start.sh: No such file or directory

/bin/bash: start.sh: No such file or directory

/bin/bash: start.sh: No such file or directory

The output from the Portainer LOG:

2025/07/25 07:31AM ERR github.com/portainer/portainer/api/http/handler/docker/containers/recreate.go:88 > cannot find webhook by containerId | error="object not found inside the database" containerId=container-key

Container_Key i remove

[dwantstocode]

I am in the same boat. Seems the update did happen by redeploying the immich stack but the immich-server is stuck as seen below in logs

[dwantstocode]

it took a while, but its all good and working fine. I guess the database migration was very slow.