#Unraid DockerCompose Update Stack not working

1 messages · Page 1 of 1 (latest)

dusty kelp
#

I ran the "Update Stack" command, waited for the "Connection Closed" notification and clicked done.
Refreshed Immich web ui and it was not updated.

So i returned to Unraid and ran Update Stack again and noticed that all the containers were up to date,
but the creating container step fails with the error message

Error response from daemon: Conflict. The container name "/immich_redis" is already in use by container

An unraid reboot did not fix the issue, I'm still on the older version of Immich (v1.106.4) instead of the latest (1.112.1)
Running Update Stack after the reboot resulted in the same conflict error.

high willowBOT
#

:wave: Hey @dusty kelp,

Thanks for reaching out to us. Please follow the recommended actions below; this will help us be more effective in our support effort and leave more time for building Immich immich.

References

Checklist

  1. :blue_square: I have verified I'm on the latest release(note that mobile app releases may take some time).
  2. :blue_square: I have read applicable release notes.
  3. :blue_square: I have reviewed the FAQs for known issues.
  4. :blue_square: I have reviewed Github for known issues.
  5. :blue_square: I have tried accessing Immich via local ip (without a custom reverse proxy).
  6. :blue_square: I have uploaded the relevant logs, docker compose, and .env files, making sure to use code formatting.
  7. :blue_square: I have 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)

If this ticket can be closed you can use the /close command, and re-open it later if needed.

lapis quartz
#

are you running Portainer?

#

please try to use the command line and following the steps

#

bring down the stack

#

remove the container with docker container prune

#

then docker compose pull

#

and finally docker compose up

dusty kelp
#

I'm running portainer, but i've never launched the cli in portainer, i've only ever launched the console inside of a specific container.

#

how do i launch the command line? Cant see a way to do it from unraid and i'm unfamiliar with how to get there from portainer.

#

nm, got it to load in unraid, attempting to follow the above steps

dusty kelp
#

That did the trick. Is there a way to prevent that from happening in the future? does the Update Stack not work as intended?