diff --git a/images/docker-socket-proxy/index.html b/images/docker-socket-proxy/index.html index 72f379a8d4..dde9718b53 100644 --- a/images/docker-socket-proxy/index.html +++ b/images/docker-socket-proxy/index.html @@ -1,4 +1,4 @@ - socket-proxy - LinuxServer.io
Skip to content

linuxserver.io

Blog Discord Discourse Fleet GitHub Open Collective

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

Scarf.io pulls GitHub Stars GitHub Release GitHub Package Repository GitLab Container Registry Quay.io Docker Pulls Docker Stars Jenkins Build LSIO CI

Socket-proxy is a security-enhanced proxy for the Docker Socket.

socket-proxy

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-<version tag>
arm64 ✅ arm64v8-<version tag>
armhf ❌

Application Setup

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.

Usage

To help you get started creating a container from this image you can either use docker-compose or the docker cli.

---
+ socket-proxy - LinuxServer.io      
 
 
  
 
  
 
 
 
 
  
 
 
 
 
 
  
 
 
 
 
   
linuxserver.io
 
Blog Discord Discourse Fleet GitHub Open Collective
 
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
 
Scarf.io pulls GitHub Stars GitHub Release GitHub Package Repository GitLab Container Registry Quay.io Docker Pulls Docker Stars Jenkins Build
 
Socket-proxy is a security-enhanced proxy for the Docker Socket.
 
socket-proxy
 
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-<version tag> 
 
 arm64 ✅ arm64v8-<version tag> 
 
 armhf ❌  
  
 
Application Setup
 
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.
    •  
 
Usage
 
To help you get started creating a container from this image you can either use docker-compose or the docker cli.
  
---
 services:
   socket-proxy:
     image: lscr.io/linuxserver/socket-proxy:latest
diff --git a/sitemap.xml.gz b/sitemap.xml.gz
index c8871656b4..bcf6beddac 100644
Binary files a/sitemap.xml.gz and b/sitemap.xml.gz differ