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.

  • DeltaTangoLima@reddrefuge.com
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    7 months ago

    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.sock have problems with it.