We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.
Simply pulling lscr.io/linuxserver/socket-proxy:latest should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
This container is a fork of https://github.com/Tecnativa/docker-socket-proxy and as such does not follow our usual container conventions. It does not support mods or custom scripts/services, or running as a user other than root (or the docker user in a rootless environment).
The container should be run on the same docker network as the service(s) using it. Most containers that would normally connect to a mounted docker.sock can have their endpoint overridden using the DOCKER_HOST environment variable if they do not offer the option in their configuration; it should typically be pointed to tcp://socket-proxy:2375.
Never expose this container's port to a public network. It should be treated the same way you would treat the docker socket or TCP endpoint.
Revoke access to any API section that you consider your service should not need.
To see the versions of the API your Docker daemon and client support, use docker version and check the API version.
Read the docs for the API version you are using for an explanation of all the available endpoints.
We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.
Simply pulling lscr.io/linuxserver/socket-proxy:latest should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
This container is a fork of https://github.com/Tecnativa/docker-socket-proxy and as such does not follow our usual container conventions. It does not support mods or custom scripts/services, or running as a user other than root (or the docker user in a rootless environment).
The container should be run on the same docker network as the service(s) using it. Most containers that would normally connect to a mounted docker.sock can have their endpoint overridden using the DOCKER_HOST environment variable if they do not offer the option in their configuration; it should typically be pointed to tcp://socket-proxy:2375.
Never expose this container's port to a public network. It should be treated the same way you would treat the docker socket or TCP endpoint.
Revoke access to any API section that you consider your service should not need.
To see the versions of the API your Docker daemon and client support, use docker version and check the API version.
Read the docs for the API version you are using for an explanation of all the available endpoints.