kopia lustrzana https://github.com/linuxserver/docker-documentation
Bot Updating Documentation
LinuxServer-CI
rodzic
b3d39cd7b9
commit
5eee3ecf48
|
|
@ -0,0 +1,314 @@
|
|||
---
|
||||
title: socket-proxy
|
||||
---
|
||||
<!-- DO NOT EDIT THIS FILE MANUALLY -->
|
||||
<!-- Please read https://github.com/linuxserver/docker-socket-proxy/blob/main/.github/CONTRIBUTING.md -->
|
||||
[](https://linuxserver.io)
|
||||
|
||||
[](https://blog.linuxserver.io "all the things you can do with our containers including How-To guides, opinions and much more!")
|
||||
[](https://discord.gg/YWrKVTn "realtime support / chat with the community and the team.")
|
||||
[](https://discourse.linuxserver.io "post on our community forum.")
|
||||
[](https://fleet.linuxserver.io "an online web interface which displays all of our maintained images.")
|
||||
[](https://github.com/linuxserver "view the source for all of our repositories.")
|
||||
[](https://opencollective.com/linuxserver "please consider helping us by either donating or contributing to our budget")
|
||||
|
||||
The [LinuxServer.io](https://linuxserver.io) team brings you another container release.
|
||||
|
||||
Find us at:
|
||||
|
||||
* [Blog](https://blog.linuxserver.io) - all the things you can do with our containers including How-To guides, opinions and much more!
|
||||
* [Discord](https://discord.gg/YWrKVTn) - realtime support / chat with the community and the team.
|
||||
* [Discourse](https://discourse.linuxserver.io) - post on our community forum.
|
||||
* [Fleet](https://fleet.linuxserver.io) - an online web interface which displays all of our maintained images.
|
||||
* [GitHub](https://github.com/linuxserver) - view the source for all of our repositories.
|
||||
* [Open Collective](https://opencollective.com/linuxserver) - please consider helping us by either donating or contributing to our budget
|
||||
|
||||
# [linuxserver/socket-proxy](https://github.com/linuxserver/docker-socket-proxy)
|
||||
|
||||
[](https://scarf.sh/gateway/linuxserver-ci/docker/linuxserver%2Fsocket-proxy)
|
||||
[](https://github.com/linuxserver/docker-socket-proxy)
|
||||
[](https://github.com/linuxserver/docker-socket-proxy/releases)
|
||||
[](https://github.com/linuxserver/docker-socket-proxy/packages)
|
||||
[](https://gitlab.com/linuxserver.io/docker-socket-proxy/container_registry)
|
||||
[](https://quay.io/repository/linuxserver.io/socket-proxy)
|
||||
[](https://hub.docker.com/r/linuxserver/socket-proxy)
|
||||
[](https://hub.docker.com/r/linuxserver/socket-proxy)
|
||||
[](https://ci.linuxserver.io/job/Docker-Pipeline-Builders/job/docker-socket-proxy/job/master/)
|
||||
[](https://ci-tests.linuxserver.io/linuxserver/socket-proxy/latest/index.html)
|
||||
|
||||
[Socket-proxy](https://github.com/Tecnativa/docker-socket-proxy) is a security-enhanced proxy for the Docker Socket.
|
||||
|
||||
[](https://github.com/Tecnativa/docker-socket-proxy)
|
||||
|
||||
## Supported Architectures
|
||||
|
||||
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://distribution.github.io/distribution/spec/manifest-v2-2/#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
|
||||
|
||||
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](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](https://docs.docker.com/engine/api/) 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.
|
||||
|
||||
### docker-compose (recommended, [click here for more info](https://docs.linuxserver.io/general/docker-compose))
|
||||
|
||||
```yaml
|
||||
---
|
||||
services:
|
||||
socket-proxy:
|
||||
image: lscr.io/linuxserver/socket-proxy:latest
|
||||
container_name: socket-proxy
|
||||
environment:
|
||||
- EVENTS=1 #optional
|
||||
- PING=1 #optional
|
||||
- VERSION=1 #optional
|
||||
- AUTH=0 #optional
|
||||
- SECRETS=0 #optional
|
||||
- POST=0 #optional
|
||||
- BUILD=0 #optional
|
||||
- COMMIT=0 #optional
|
||||
- CONFIGS=0 #optional
|
||||
- CONTAINERS=0 #optional
|
||||
- ALLOW_START=0 #optional
|
||||
- ALLOW_STOP=0 #optional
|
||||
- ALLOW_RESTARTS=0 #optional
|
||||
- DISTRIBUTION=0 #optional
|
||||
- EXEC=0 #optional
|
||||
- IMAGES=0 #optional
|
||||
- INFO=0 #optional
|
||||
- LOG_LEVEL=info #optional
|
||||
- NETWORKS=0 #optional
|
||||
- NODES=0 #optional
|
||||
- PLUGINS=0 #optional
|
||||
- SERVICES=0 #optional
|
||||
- SESSION=0 #optional
|
||||
- SWARM=0 #optional
|
||||
- SYSTEM=0 #optional
|
||||
- TASKS=0 #optional
|
||||
- VOLUMES=0 #optional
|
||||
- DISABLE_IPV6=0 #optional
|
||||
volumes:
|
||||
- /var/run/docker.sock:/var/run/docker.sock:ro
|
||||
restart: unless-stopped
|
||||
read_only: true
|
||||
tmpfs:
|
||||
- /run
|
||||
```
|
||||
|
||||
### docker cli ([click here for more info](https://docs.docker.com/engine/reference/commandline/cli/))
|
||||
|
||||
```bash
|
||||
docker run -d \
|
||||
--name=socket-proxy \
|
||||
-e EVENTS=1 `#optional` \
|
||||
-e PING=1 `#optional` \
|
||||
-e VERSION=1 `#optional` \
|
||||
-e AUTH=0 `#optional` \
|
||||
-e SECRETS=0 `#optional` \
|
||||
-e POST=0 `#optional` \
|
||||
-e BUILD=0 `#optional` \
|
||||
-e COMMIT=0 `#optional` \
|
||||
-e CONFIGS=0 `#optional` \
|
||||
-e CONTAINERS=0 `#optional` \
|
||||
-e ALLOW_START=0 `#optional` \
|
||||
-e ALLOW_STOP=0 `#optional` \
|
||||
-e ALLOW_RESTARTS=0 `#optional` \
|
||||
-e DISTRIBUTION=0 `#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 PLUGINS=0 `#optional` \
|
||||
-e SERVICES=0 `#optional` \
|
||||
-e SESSION=0 `#optional` \
|
||||
-e SWARM=0 `#optional` \
|
||||
-e SYSTEM=0 `#optional` \
|
||||
-e TASKS=0 `#optional` \
|
||||
-e VOLUMES=0 `#optional` \
|
||||
-e DISABLE_IPV6=0 `#optional` \
|
||||
-v /var/run/docker.sock:/var/run/docker.sock:ro \
|
||||
--restart unless-stopped \
|
||||
--read-only \
|
||||
--tmpfs /run \
|
||||
lscr.io/linuxserver/socket-proxy:latest
|
||||
```
|
||||
|
||||
## Parameters
|
||||
|
||||
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 EVENTS=1` | `/events` |
|
||||
| `-e PING=1` | `/_ping` |
|
||||
| `-e VERSION=1` | `/version` |
|
||||
| `-e AUTH=0` | `/auth` |
|
||||
| `-e SECRETS=0` | `/secrets` |
|
||||
| `-e POST=0` | When set to `0`, only `GET` and `HEAD` operations are allowed, making API access read-only. |
|
||||
| `-e BUILD=0` | `/build` |
|
||||
| `-e COMMIT=0` | `/commit` |
|
||||
| `-e CONFIGS=0` | `/configs` |
|
||||
| `-e CONTAINERS=0` | `/containers` |
|
||||
| `-e ALLOW_START=0` | `/containers/id/start` |
|
||||
| `-e ALLOW_STOP=0` | `/containers/id/stop` |
|
||||
| `-e ALLOW_RESTARTS=0` | `/containers/id/stop`, `/containers/id/restart`, and `/containers/id/kill` |
|
||||
| `-e DISTRIBUTION=0` | `/distribution` |
|
||||
| `-e EXEC=0` | `/exec` & `/containers/{id}/exec` |
|
||||
| `-e IMAGES=0` | `/images` |
|
||||
| `-e INFO=0` | `/info` |
|
||||
| `-e LOG_LEVEL=info` | Default value is `info`. Possible values are: `debug`, `info`, `notice`, `warning`, `err`, `crit`, `alert`, and `emerg`. |
|
||||
| `-e NETWORKS=0` | `/networks` |
|
||||
| `-e NODES=0` | `/nodes` |
|
||||
| `-e PLUGINS=0` | `/plugins` |
|
||||
| `-e SERVICES=0` | `/services` |
|
||||
| `-e SESSION=0` | `/session` |
|
||||
| `-e SWARM=0` | `/swarm` |
|
||||
| `-e SYSTEM=0` | `/system` |
|
||||
| `-e TASKS=0` | `/tasks` |
|
||||
| `-e VOLUMES=0` | `/volumes` |
|
||||
| `-e DISABLE_IPV6=0` | Set to `1` to disable IPv6 bindings in scenarios where the host cannot support it. |
|
||||
| `-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:
|
||||
|
||||
```bash
|
||||
docker exec -it socket-proxy /bin/sh
|
||||
```
|
||||
|
||||
* To monitor the logs of the container in realtime:
|
||||
|
||||
```bash
|
||||
docker logs -f socket-proxy
|
||||
```
|
||||
|
||||
* Container version number:
|
||||
|
||||
```bash
|
||||
docker inspect -f '{{ index .Config.Labels "build_version" }}' socket-proxy
|
||||
```
|
||||
|
||||
* Image version number:
|
||||
|
||||
```bash
|
||||
docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/socket-proxy:latest
|
||||
```
|
||||
|
||||
## Updating 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](#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:
|
||||
* All images:
|
||||
|
||||
```bash
|
||||
docker-compose pull
|
||||
```
|
||||
|
||||
* Single image:
|
||||
|
||||
```bash
|
||||
docker-compose pull socket-proxy
|
||||
```
|
||||
|
||||
* Update containers:
|
||||
* All containers:
|
||||
|
||||
```bash
|
||||
docker-compose up -d
|
||||
```
|
||||
|
||||
* Single container:
|
||||
|
||||
```bash
|
||||
docker-compose up -d socket-proxy
|
||||
```
|
||||
|
||||
* You can also remove the old dangling images:
|
||||
|
||||
```bash
|
||||
docker image prune
|
||||
```
|
||||
|
||||
### Via Docker Run
|
||||
|
||||
* Update the image:
|
||||
|
||||
```bash
|
||||
docker pull lscr.io/linuxserver/socket-proxy:latest
|
||||
```
|
||||
|
||||
* Stop the running container:
|
||||
|
||||
```bash
|
||||
docker stop socket-proxy
|
||||
```
|
||||
|
||||
* Delete the container:
|
||||
|
||||
```bash
|
||||
docker rm socket-proxy
|
||||
```
|
||||
|
||||
* You can also remove the old dangling images:
|
||||
|
||||
```bash
|
||||
docker image prune
|
||||
```
|
||||
|
||||
### Image Update Notifications - Diun (Docker Image Update Notifier)
|
||||
|
||||
**tip**: We recommend [Diun](https://crazymax.dev/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:
|
||||
|
||||
```bash
|
||||
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 x86_64 hardware using `multiarch/qemu-user-static`
|
||||
|
||||
```bash
|
||||
docker run --rm --privileged multiarch/qemu-user-static:register --reset
|
||||
```
|
||||
|
||||
Once registered you can define the dockerfile to use with `-f Dockerfile.aarch64`.
|
||||
|
||||
## Versions
|
||||
|
||||
* **07.04.24:** - Initial Release.
|
||||
Ładowanie…
Reference in New Issue