Last edited:
Hi
Just before Christmas I managed my first docker container, Qbittorrent (thanks again Rusty) and now I have (well, had) Portainer, PiHole and Bitwarden_RS running sweet and true. Oh yes, what an expert I am!!!
Until about thirty minutes ago when I tried to update my first container, the aforementioned Portainer. So I followed the basic steps, standard everywhere and here from @wwwampy. Download, clear, start. Easy. This must be from version 2.0.0 to 2.0.1, so nothing major.
Now I have the error mentioned above, specifically http error: Unable to proxy the request via the Docker socket (err=dial unix /var/run/docker.sock: connect: no such file or directory) (code=500).
I guess the error starts with background schedule error (endpoint snapshot). Unable to create snapshot (endpoint=local, URL=unix:///var/run/docker.sock) (err=Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?) and then there are a few Invalid JWT token errors and finally the unable to proxy one.
I looked at a similar problem and no joy. I set the local Endpoint value to "10.0.10.32", the address of my NAS. (This was not required on my initial install.)
What on earth??? Nothing else was changed. Nothing. Perhaps I misunderstand the Clear command when updating.
Totally lost. A true expert... Any thoughts will be gratefully received!
Just before Christmas I managed my first docker container, Qbittorrent (thanks again Rusty) and now I have (well, had) Portainer, PiHole and Bitwarden_RS running sweet and true. Oh yes, what an expert I am!!!
Until about thirty minutes ago when I tried to update my first container, the aforementioned Portainer. So I followed the basic steps, standard everywhere and here from @wwwampy. Download, clear, start. Easy. This must be from version 2.0.0 to 2.0.1, so nothing major.
Now I have the error mentioned above, specifically http error: Unable to proxy the request via the Docker socket (err=dial unix /var/run/docker.sock: connect: no such file or directory) (code=500).
I guess the error starts with background schedule error (endpoint snapshot). Unable to create snapshot (endpoint=local, URL=unix:///var/run/docker.sock) (err=Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?) and then there are a few Invalid JWT token errors and finally the unable to proxy one.
I looked at a similar problem and no joy. I set the local Endpoint value to "10.0.10.32", the address of my NAS. (This was not required on my initial install.)
What on earth??? Nothing else was changed. Nothing. Perhaps I misunderstand the Clear command when updating.
Totally lost. A true expert... Any thoughts will be gratefully received!