What gives? I have to stop Portainer, restart Supervisor container and update. And start Portainer. Any way to prevent HA from detecting it? Renaming the container? It is really idiotic.
Are you able to share any additional details about your setup? How are you running HA?Scratch that - I just realised that you mentioned the Supervisor container, so that kinda tells me how you’re running it. I suspect the problem is that both Portainer and the Supervisor container want to maintain a lock of some sort on
docker.sock.But I run HA in its own container, so I don’t have any experience with the Supervisor container myself. I do run everything with Portainer though, and I’ve seen other things that wanted to use
docker.sockhave problems with it.Running in docker, Ubuntu server 22.04
I edited my reply above. Could it be that both want to lock
docker.sock?
Im usually updating containers using portainer:
- Stop container
- Recreate (Re-pull image checked)
- Done
But some containers give error, so I have to:
- Delete container
- Redeploy the stack
- Done
It might be useless for your problem, but posting this just in case. For the same reason Ill try dockge and see if updates are easier
