Docker.sock permission debian trixie #12863
Unanswered
netsrot303
asked this question in
Help
Replies: 2 comments
-
|
@netsrot303 Are you deploying Portainer via sudo? This is a permission related issue on your system, not sure what changes are in the new Debian upgrade but could be worth asking on their forums as well |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I deploy portainer as root user. i also asked in docker forum. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Ask a Question!
Hello, I have a problem after updating from Debian Bookworm to Debian Trixie. I had several containers running under Bookworm, including Portainer. However, after the update to debian trixie, I no longer have access to docker.sock, which means Portainer cannot access docker.sock to manage the other running containers. Of course, I passed docker.sock to Portainer -v /var/run/docker.sock:/var/run/docker.sock. Now, when I try to add the Docker environment to Portainer via the socket, I get the error message “Permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Head “http://%2Fvar%2Frun%2Fdocker.sock/_ping”: dial unix /var/run/docker.sock: socket: permission denied.”
Do you have any Ideas?
Beta Was this translation helpful? Give feedback.
All reactions