Socket proxy fails #12501
Replies: 2 comments 2 replies
-
(I replaced container name below to match yours) There should be a new environment there, which uses "API" as the connection type and "tcp://socket-proxy:2375" for the Docker API URL. I do have this in my compose file:
But it has been a while since I set it up and I forgot if just including this environment variable does the trick (if it does not, what I actually forgot was if I added the new environment manually, switched to it and removed the default one you still see). |
Beta Was this translation helpful? Give feedback.
-
Even though I added socket-proxy to my environment, and also deleted the default environment, I still get log error. portainer | 2025/01/27 09:03PM WRN github.com/portainer/portainer@v0.6.1-0.20240906003626-280ca22aebb2/api/platform/platform.go:70 >failed to retrieve docker info | error="Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?" |
Beta Was this translation helpful? Give feedback.
-
Ask a Question!
I'm using the following docker compose file to launch Portainer using a socket-proxy:
Yet this fails
portainer | 2025/01/24 10:48PM WRN github.com/portainer/[email protected]/api/platform/platform.go:70 > failed to retrieve docker info | error="Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?"
When I log in, I see this:
![](https://camo.githubusercontent.com/4f351b7b87a42abab70b7f8cb1e77dec5b249357f572602fecefeadaecad2704/68747470733a2f2f692e696d6775722e636f6d2f7933526246324f2e706e67)
instead of socket-proxy.
What am I missing?
Beta Was this translation helpful? Give feedback.
All reactions