You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I keep access to the docker socket behind a proxy, so mapping /var/run/docker.sock doesn't work for my use case. Instead, all of my containers that need access to the docker socket get access through tcp://socket-proxy:2375 via a specific command or environment variable. I'd like to give this a shot to compare to portainer, but won't be able to until this is supported.
I did not realize that was a built in variable, I've used it in other containers, but I always thought that was container specific. Thanks for the info, that got me going.
I keep access to the docker socket behind a proxy, so mapping /var/run/docker.sock doesn't work for my use case. Instead, all of my containers that need access to the docker socket get access through tcp://socket-proxy:2375 via a specific command or environment variable. I'd like to give this a shot to compare to portainer, but won't be able to until this is supported.
https://github.com/fluencelabs/docker-socket-proxy
The text was updated successfully, but these errors were encountered: