Socket-proxy
Container
This container needs special attention. Please check https://hub.docker.com/r/linuxserver/socket-proxy for details.
Image details
Configuration
TypeContainerlinuxlinuxserver/socket-proxy:latest80:80/tcp/config : /srv/lsio/socket-proxy/configPUID=1000PGID=1000TZ=Etc/UTCunless-stoppedTemplate by technorabilia
Notes
Ensure to create the following volume directories on the host file system, or modify the paths in the volume mapping section under the advanced options below, as needed.
mkdir -p /srv/lsio/socket-proxy/config
Standalone Install
Select an install method, to see config/commands for deploying Socket-proxy
Install on Portainer
Import all app templates into your Portainer instance, for easy 1-click deploys
- Ensure both Docker and Portainer are installed, and up-to-date
- Log into your Portainer web UI
- Under Settings → App Templates, paste the below URL
- Head to Home → App Templates, and the list of apps will show up
- Select Socket-proxy, fill in any config options, and hit Deploy
Template Import URL
https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me
More install options in our documentation.

The LinuxServer.io team brings you another container release.
Find us at:
- Blog - all the things you can do with our containers including How-To guides, opinions and much more!
- Discord - realtime support / chat with the community and the team.
- Discourse - post on our community forum.
- Fleet - an online web interface which displays all of our maintained images.
- GitHub - view the source for all of our repositories.
- Open Collective - please consider helping us by either donating or contributing to our budget
linuxserver/socket-proxy
The Socket Proxy is a security-enhanced proxy which allows you to apply access rules to the Docker socket, limiting the attack surface for containers such as watchtower or Traefik that need to use it.

Supported Architectures
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.The architectures supported by this image are:
| Architecture | Available | Tag |
|---|---|---|
| x86-64 | ✅ | amd64-\ |
| riscv64 | ✅ | riscv64-\ |
| arm64 | ✅ | arm64v8-\ |
| armhf | ❌ |
Application Setup
This container is conceptually based on 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. It is designed to act as a drop-in replacement for the Tecnativa container.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 versionand check theAPI version. - Read the docs for the API version you are using for an explanation of all the available endpoints.
Podman / libpod API
Podman exposes two API groups on the same socket: the Docker-compatible API (controlled by the existing env vars above) and the libpod-native API prefixed with/libpod/. The LIBPOD_* environment variables control access to the libpod endpoints independently of their Docker-compat equivalents.For example, to use prometheus-podman-exporter, enable:
- LIBPOD_CONTAINERS=1
- LIBPOD_INFO=1
- LIBPOD_NETWORKS=1
- LIBPOD_PODS=1
- LIBPOD_VOLUMES=1
- LIBPOD_IMAGES=1
- LIBPOD_EVENTS=1Point the exporter at
tcp://socket-proxy:2375 using CONTAINER_HOST. LIBPOD_PING and LIBPOD_VERSION are enabled by default (like their Docker-compat counterparts PING and VERSION).Rootless Podman as a non-root user
Under rootless Podman the container process runs asroot inside its user namespace by default. You can go a step further and drop root inside the container as well, running the proxy as an unprivileged user such as nobody (UID/GID 65534). Two things need to be handled for this to work:- Socket ownership. The rootless Podman socket (
$XDG_RUNTIME_DIR/podman/podman.sock) is owned by your host user. That user maps torootinside the container's namespace, so a non-root user in the container cannot read it. Use--userns=keep-id:uid=65534,gid=65534to map your host user onto UID/GID65534inside the container, sonobodyowns the socket and can proxy it. - A writable
/run. The entrypoint renders the HAProxy config into/run/haproxyat startup, so/runmust be writable by the non-root user. Mount it as a tmpfs withmode=1777(this also satisfies read-only operation).
Example
podman run:podman run -d \
--name=socket-proxy \
--user 65534:65534 \
--userns=keep-id:uid=65534,gid=65534 \
-e CONTAINERS=1 `#optional` \
-e LIBPOD_CONTAINERS=1 `#optional` \
-e POST=0 `#optional` \
-v $XDG_RUNTIME_DIR/podman/podman.sock:/var/run/docker.sock:ro \
-p 2375:2375 \
--read-only \
--tmpfs /run:rw,mode=1777 \
--restart unless-stopped \
lscr.io/linuxserver/socket-proxy:latestOr as a rootless Quadlet unit (
~/.config/containers/systemd/socket-proxy.container), started with systemctl --user daemon-reload && systemctl --user start socket-proxy:[Container]
ContainerName=socket-proxy
Image=lscr.io/linuxserver/socket-proxy:latest
User=65534:65534
UserNS=keep-id:uid=65534,gid=65534
Environment=CONTAINERS=1
Environment=LIBPOD_CONTAINERS=1
Environment=POST=0
Volume=%t/podman/podman.sock:/var/run/docker.sock:ro
PublishPort=2375:2375
ReadOnly=true
Tmpfs=/run:rw,mode=1777
[Install]
WantedBy=default.target(
%t expands to $XDG_RUNTIME_DIR.) Enable the socket first with systemctl --user enable --now podman.socket.!NOTE On SELinux-enforcing hosts (e.g. Fedora/RHEL), add--security-opt label=disableto thepodman run(orSecurityLabelDisable=trueto the Quadlet) so the container can access the mounted socket.
Read-Only Operation
This image can be run with a read-only container filesystem. For details please read the docs.Usage
To help you get started creating a container from this image you can either use docker compose or the docker cli.>!NOTE >Unless a parameter is flaged as 'optional', it is mandatory and a value must be provided.
docker compose (recommended, click here for more info)
---
services:
socket-proxy:
image: lscr.io/linuxserver/socket-proxy:latest
container_name: socket-proxy
environment:
- ALLOW_START=0 #optional
- ALLOW_STOP=0 #optional
- ALLOW_RESTARTS=0 #optional
- ALLOW_PAUSE=0 #optional
- ALLOW_UNPAUSE=0 #optional
- AUTH=0 #optional
- BUILD=0 #optional
- COMMIT=0 #optional
- CONFIGS=0 #optional
- CONTAINERS=0 #optional
- DISABLE_IPV6=0 #optional
- DISTRIBUTION=0 #optional
- EVENTS=1 #optional
- EXEC=0 #optional
- IMAGES=0 #optional
- INFO=0 #optional
- LOG_LEVEL=info #optional
- NETWORKS=0 #optional
- NODES=0 #optional
- PING=1 #optional
- PLUGINS=0 #optional
- POST=0 #optional
- SECRETS=0 #optional
- SERVICES=0 #optional
- SESSION=0 #optional
- SWARM=0 #optional
- SYSTEM=0 #optional
- TASKS=0 #optional
- TZ=Etc/UTC #optional
- VERSION=1 #optional
- VOLUMES=0 #optional
- LIBPOD_ALLOW_PAUSE=0 #optional
- LIBPOD_ALLOW_POD_PAUSE=0 #optional
- LIBPOD_ALLOW_POD_RESTARTS=0 #optional
- LIBPOD_ALLOW_POD_START=0 #optional
- LIBPOD_ALLOW_POD_STOP=0 #optional
- LIBPOD_ALLOW_POD_UNPAUSE=0 #optional
- LIBPOD_ALLOW_RESTARTS=0 #optional
- LIBPOD_ALLOW_START=0 #optional
- LIBPOD_ALLOW_STOP=0 #optional
- LIBPOD_ALLOW_UNPAUSE=0 #optional
- LIBPOD_CONTAINERS=0 #optional
- LIBPOD_EVENTS=0 #optional
- LIBPOD_EXEC=0 #optional
- LIBPOD_GENERATE=0 #optional
- LIBPOD_IMAGES=0 #optional
- LIBPOD_INFO=0 #optional
- LIBPOD_MANIFESTS=0 #optional
- LIBPOD_NETWORKS=0 #optional
- LIBPOD_PING=1 #optional
- LIBPOD_PLAY=0 #optional
- LIBPOD_PODS=0 #optional
- LIBPOD_SECRETS=0 #optional
- LIBPOD_SYSTEM=0 #optional
- LIBPOD_VERSION=1 #optional
- LIBPOD_VOLUMES=0 #optional
volumes:
- /var/run/docker.sock:/var/run/docker.sock:ro
restart: unless-stopped
read_only: true
tmpfs:
- /rundocker cli (click here for more info)
docker run -d \
--name=socket-proxy \
-e ALLOW_START=0 `#optional` \
-e ALLOW_STOP=0 `#optional` \
-e ALLOW_RESTARTS=0 `#optional` \
-e ALLOW_PAUSE=0 `#optional` \
-e ALLOW_UNPAUSE=0 `#optional` \
-e AUTH=0 `#optional` \
-e BUILD=0 `#optional` \
-e COMMIT=0 `#optional` \
-e CONFIGS=0 `#optional` \
-e CONTAINERS=0 `#optional` \
-e DISTRIBUTION=0 `#optional` \
-e DISABLE_IPV6=0 `#optional` \
-e EVENTS=1 `#optional` \
-e EXEC=0 `#optional` \
-e IMAGES=0 `#optional` \
-e INFO=0 `#optional` \
-e LOG_LEVEL=info `#optional` \
-e NETWORKS=0 `#optional` \
-e NODES=0 `#optional` \
-e PING=1 `#optional` \
-e PLUGINS=0 `#optional` \
-e POST=0 `#optional` \
-e SECRETS=0 `#optional` \
-e SERVICES=0 `#optional` \
-e SESSION=0 `#optional` \
-e SWARM=0 `#optional` \
-e SYSTEM=0 `#optional` \
-e TASKS=0 `#optional` \
-e TZ=Etc/UTC `#optional` \
-e VERSION=1 `#optional` \
-e VOLUMES=0 `#optional` \
-e LIBPOD_ALLOW_PAUSE=0 `#optional` \
-e LIBPOD_ALLOW_POD_PAUSE=0 `#optional` \
-e LIBPOD_ALLOW_POD_RESTARTS=0 `#optional` \
-e LIBPOD_ALLOW_POD_START=0 `#optional` \
-e LIBPOD_ALLOW_POD_STOP=0 `#optional` \
-e LIBPOD_ALLOW_POD_UNPAUSE=0 `#optional` \
-e LIBPOD_ALLOW_RESTARTS=0 `#optional` \
-e LIBPOD_ALLOW_START=0 `#optional` \
-e LIBPOD_ALLOW_STOP=0 `#optional` \
-e LIBPOD_ALLOW_UNPAUSE=0 `#optional` \
-e LIBPOD_CONTAINERS=0 `#optional` \
-e LIBPOD_EVENTS=0 `#optional` \
-e LIBPOD_EXEC=0 `#optional` \
-e LIBPOD_GENERATE=0 `#optional` \
-e LIBPOD_IMAGES=0 `#optional` \
-e LIBPOD_INFO=0 `#optional` \
-e LIBPOD_MANIFESTS=0 `#optional` \
-e LIBPOD_NETWORKS=0 `#optional` \
-e LIBPOD_PING=1 `#optional` \
-e LIBPOD_PLAY=0 `#optional` \
-e LIBPOD_PODS=0 `#optional` \
-e LIBPOD_SECRETS=0 `#optional` \
-e LIBPOD_SYSTEM=0 `#optional` \
-e LIBPOD_VERSION=1 `#optional` \
-e LIBPOD_VOLUMES=0 `#optional` \
-v /var/run/docker.sock:/var/run/docker.sock:ro \
--restart unless-stopped \
--read-only \
--tmpfs /run \
lscr.io/linuxserver/socket-proxy:latestParameters
Containers are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate<external>:<internal> respectively. For example, -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080 outside the container.| Parameter | Function |
|---|---|
-e ALLOWSTART=0 | /containers/{id}/start - This option will work even if POST=0 |
-e ALLOWSTOP=0 | /containers/{id}/stop - This option will work even if POST=0 |
-e ALLOWRESTARTS=0 | /containers/{id}/stop, /containers/{id}/restart, and /containers/{id}/kill - This option will work even if POST=0 |
-e ALLOWPAUSE=0 | /containers/{id}/pause - This option will work even if POST=0 |
-e ALLOWUNPAUSE=0 | /containers/{id}/unpause - This option will work even if POST=0 |
-e AUTH=0 | /auth |
-e BUILD=0 | /build |
-e COMMIT=0 | /commit |
-e CONFIGS=0 | /configs |
-e CONTAINERS=0 | /containers |
-e DISTRIBUTION=0 | /distribution |
-e DISABLEIPV6=0 | Set to 1 to prevent binding to the IPv6 interface for legacy systems that cannot support IPv6. |
-e EVENTS=1 | /events |
-e EXEC=0 | /exec & /containers/{id}/exec |
-e IMAGES=0 | /images |
-e INFO=0 | /info |
-e LOGLEVEL=info | Possible values are: debug, info, notice, warning, err, crit, alert and emerg. Defaults to info. |
-e NETWORKS=0 | /networks |
-e NODES=0 | /nodes |
-e PING=1 | /ping |
-e PLUGINS=0 | /plugins |
-e POST=0 | When set to 0, only GET and HEAD operations are allowed, making API access read-only. |
-e SECRETS=0 | /secrets |
-e SERVICES=0 | /services |
-e SESSION=0 | /session |
-e SWARM=0 | /swarm |
-e SYSTEM=0 | /system |
-e TASKS=0 | /tasks |
-e TZ=Etc/UTC | Set container timezone |
-e VERSION=1 | /version |
-e VOLUMES=0 | /volumes |
| Podman libpod API | |
-e LIBPODALLOWSTART=0 | /libpod/containers/{id}/start - This option will work even if POST=0 |
-e LIBPODALLOWSTOP=0 | /libpod/containers/{id}/stop - This option will work even if POST=0 |
-e LIBPODALLOWRESTARTS=0 | /libpod/containers/{id}/stop, /libpod/containers/{id}/restart, and /libpod/containers/{id}/kill - This option will work even if POST=0 |
-e LIBPODALLOWPAUSE=0 | /libpod/containers/{id}/pause - This option will work even if POST=0 |
-e LIBPODALLOWUNPAUSE=0 | /libpod/containers/{id}/unpause - This option will work even if POST=0 |
-e LIBPODALLOWPODSTART=0 | /libpod/pods/{name}/start - This option will work even if POST=0 |
-e LIBPODALLOWPODSTOP=0 | /libpod/pods/{name}/stop - This option will work even if POST=0 |
-e LIBPODALLOWPODRESTARTS=0 | /libpod/pods/{name}/stop, /libpod/pods/{name}/restart, and /libpod/pods/{name}/kill - This option will work even if POST=0 |
-e LIBPODALLOWPODPAUSE=0 | /libpod/pods/{name}/pause - This option will work even if POST=0 |
-e LIBPODALLOWPODUNPAUSE=0 | /libpod/pods/{name}/unpause - This option will work even if POST=0 |
-e LIBPODCONTAINERS=0 | /libpod/containers |
-e LIBPODEVENTS=0 | /libpod/events |
-e LIBPODEXEC=0 | /libpod/exec |
-e LIBPODGENERATE=0 | /libpod/generate (systemd/kube YAML generation) |
-e LIBPODIMAGES=0 | /libpod/images |
-e LIBPODINFO=0 | /libpod/info |
-e LIBPODMANIFESTS=0 | /libpod/manifests |
-e LIBPODNETWORKS=0 | /libpod/networks |
-e LIBPODPING=1 | /libpod/ping |
-e LIBPODPLAY=0 | /libpod/play (kube play) |
-e LIBPODPODS=0 | /libpod/pods (Podman-specific pod management) |
-e LIBPODSECRETS=0 | /libpod/secrets |
-e LIBPODSYSTEM=0 | /libpod/system |
-e LIBPODVERSION=1 | /libpod/version |
-e LIBPODVOLUMES=0 | /libpod/volumes |
-v /var/run/docker.sock:ro | Mount the host docker socket into the container. |
--read-only | Make the container filesystem read-only. |
--tmpfs /run | Mount /run to tmpfs (RAM) to make it writeable. |
Support Info
- Shell access whilst the container is running:
docker exec -it socket-proxy /bin/sh- To monitor the logs of the container in realtime:
docker logs -f socket-proxy- Container version number:
docker inspect -f '{{ index .Config.Labels "build_version" }}' socket-proxy- Image version number:
docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/socket-proxy:latestUpdating Info
Most of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (noted in the relevant readme.md), we do not recommend or support updating apps inside the container. Please consult the Application Setup section above to see if it is recommended for the image.Below are the instructions for updating containers:
Via Docker Compose
- Update images:
```bash docker compose pull ```
Single image:
```bash docker compose pull socket-proxy ```
- Update containers:
```bash docker compose up -d ```
Single container:
```bash docker compose up -d socket-proxy ```
- You can also remove the old dangling images:
docker image pruneVia Docker Run
- Update the image:
docker pull lscr.io/linuxserver/socket-proxy:latest- Stop the running container:
docker stop socket-proxy- Delete the container:
docker rm socket-proxy- You can also remove the old dangling images:
docker image pruneImage Update Notifications - Diun (Docker Image Update Notifier)
>!TIP >We recommend Diun for update notifications. Other tools that automatically update containers unattended are not recommended or supported.Building locally
If you want to make local modifications to these images for development purposes or just to customize the logic:git clone https://github.com/linuxserver/docker-socket-proxy.git
cd docker-socket-proxy
docker build \
--no-cache \
--pull \
-t lscr.io/linuxserver/socket-proxy:latest .The ARM variants can be built on x8664 hardware and vice versa using
lscr.io/linuxserver/docker-qemu-staticdocker run --rm --privileged lscr.io/linuxserver/docker-qemu-static --resetOnce registered you can define the dockerfile to use with
-f Dockerfile.aarch64.Versions
- 15.06.26: - Rebase to Alpine 3.24.
- 13.06.26: - Add libpod API support for Podman via
LIBPOD_*environment variables. - 24.02.26: - Add
ALLOW_PAUSEandALLOW_UNPAUSE. - 26.12.25: - Rebase to Alpine 3.23.
- 19.08.25: - Add tzdata for localised logging timestamps.
- 03.06.25: - Rebase to Alpine 3.22. Add RISCV support.
- 08.04.25: - Add
LOG_LEVELback. - 06.04.25: - Switch back to haproxy for better handling of
docker execconnection hijacking. - 02.01.25: - Support custom read timeout values.
- 05.12.24: - Rebase to Alpine 3.21.
- 26.08.24: - Change
ALLOW_START,ALLOW_STOP, andALLOW_RESTARTSto work even withPOST=0. - 24.05.24: - Rebase to Alpine 3.20.
- 15.04.24: - Allow disabling IPv6 support for legacy devices.
- 08.04.24: - Use nginx due to haproxy's wonky websockets handling.
- 07.04.24: - Initial Release.
Serve Socket-proxy on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.
Proxying socket-proxy.example.com to http://Socket-proxy:80
Add this to your Caddyfile
socket-proxy.example.com {
reverse_proxy http://Socket-proxy:80
}Check the logs first
Nine times out of ten the logs tell you exactly what went wrong.
- In Portainer, go to Containers, click the container, then Logs. Or run
docker logs Socket-proxy - Exit codes help too:
137means killed, usually out of memory.126or127means the command inside the image is broken.
Port already in use
If deployment fails with "Bind for 0.0.0.0:80 failed: port is already allocated", something else on your server is using that port.
- Find what's using it:
sudo ss -tlnp | grep :80 - Stop the other service, or pick a different host port. In
80:80only the left number is yours to change, the right one belongs to the app.
Running but the page won't load
The container is up but nothing appears in your browser.
- Use your server's real IP:
http://your-server-ip:80. The 0.0.0.0 link Portainer shows isn't a real address. - Give it a minute after first deploy, Socket-proxy can take a while to initialise.
- Make sure your firewall allows the port, e.g.
sudo ufw allow 80
Permission denied on volumes
If the logs show "permission denied", the app can't write to its data folder on the host.
- Fix the ownership:
sudo chown -R 1000:1000 /srv/lsio/socket-proxy/config - Or set the
PUIDandPGIDvariables (defaults 1000:1000) to match your own user, found withid $USER
Image won't pull
Test the pull directly on the host: docker pull linuxserver/socket-proxy:latest
- "manifest unknown" means the tag no longer exists. This template uses
latest, so try pinning a specific version instead. - "toomanyrequests" is the Docker Hub rate limit. Log in with
docker loginto raise it. - "no space left on device" means a full disk. Reclaim space with
docker system prune
"exec format error"
This means the image was built for a different CPU architecture than your server.
- This image supports:
amd64, arm64, riscv64 - Check yours with
uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.
Container keeps restarting
The unless-stopped restart policy relaunches the app after every crash, so the real error can scroll past.
- Check the logs right after a restart, the last few lines before it died are the useful ones.
- Get the exit code with
docker inspect Socket-proxy --format '{{.State.ExitCode}}' - Still stuck? Redeploy once with the restart policy set to
noso the failure stays visible.
Raise an issue
Found something which isn't working as it should? Here's how to report it.
- Bug within the app: Open an issue within Socket-proxy's repo
- Template not working: Open an issue on technorabilia/portainer-templates
- This website not working: Open an issue on lissy93/portainer-templates
A single container
Socket-proxy runs as one container, the simplest kind of app here. Just the one image to pull and nothing else wired up alongside it.
The app image
An image is the app packed up ready to go, everything Socket-proxy needs bundled into one download. This template pulls linuxserver/socket-proxy:latest, which Docker fetches once (about 7 MB) and then starts your own copy from.
Where the image comes from
Docker pulls its images from registries, public libraries of ready-built apps. Socket-proxy's comes from Docker Hub, published by linuxserver.
Version tags
The bit after the colon in the image name is the version tag. Here it's latest, which always points at the newest build, so a redeploy can bump you to a newer release without you asking. Newest right now is 3.4.3. Pin a specific tag if you would rather stay on one version.
Which machines it runs on
Every image is built for particular CPU types. This one ships for amd64, arm64, riscv64, so it runs on both regular x86 servers and ARM boards like a Raspberry Pi.
Ports
A port is the door the app answers on. A mapping like 80:80 means it's reachable on port 80 of your server, where the left number is yours to change and the right one belongs to the app. Once it's running, open http://your-server-ip:80 in a browser. It opens:
80:80, likely the web interface
Volumes
A volume is where Socket-proxy keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:
/configfrom/srv/lsio/socket-proxy/configon the host
Environment variables
Environment variables are the settings you hand over when you deploy, things like a password or a timezone. Socket-proxy takes 3 of them, all with defaults you can leave alone or tweak:
PUID, defaults to1000. Run 'id [USER]' for the owner of the host volume directories to get the UID to use here.PGID, defaults to1000. Run 'id [USER]' for the owner of the host volume directories to get the GID to use here.TZ, defaults toEtc/UTC. Specify a timezone to use, see this list.
Restart policy
The restart policy here is unless-stopped, so Docker restarts Socket-proxy after a crash or reboot, but leaves it off when you stop it on purpose. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).
Users and permissions
The PUID and PGID settings tell it which user and group to act as on your host. Point them at your own account (find yours with id $USER) so the files it writes into your mounted folders come out owned by you rather than root.
Networking
Nothing custom is set, so Socket-proxy sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.
Container name
Once it's deployed, Portainer names the container Socket-proxy. That's what you'll spot in the containers list and use in commands like docker logs Socket-proxy.
Platform
The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.
Portainer app templates
Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Socket-proxy up. Add the template list to Portainer once, then deploying Socket-proxy is a click rather than a wall of config.