chore: use socket-proxy for traefik
All checks were successful
CI / validateComposeSyntax (push) Successful in 19s

This commit is contained in:
LRVT
2025-02-19 16:13:51 +01:00
parent 7987eb8b13
commit 70c24a7ece
3 changed files with 75 additions and 39 deletions

View File

@@ -14,7 +14,7 @@ services:
- 443 # https
- 8080 # http api dashboard
volumes:
- /var/run/docker.sock:/var/run/docker.sock:ro # ro = read-only access to the docker.sock
#- /var/run/docker.sock:/var/run/docker.sock:ro # better use socket-proxy instead
- ${DOCKER_VOLUME_STORAGE:-/mnt/docker-volumes}/traefik:/etc/traefik/ # put the provided traefik.yml and fileConfig.yml files at this location
- ${DOCKER_VOLUME_STORAGE:-/mnt/docker-volumes}/traefik/logs:/logs
environment:
@@ -30,7 +30,25 @@ services:
- host.docker.internal:172.17.0.1
networks:
- proxy
- docker-proxynet
socket-proxy:
image: lscr.io/linuxserver/socket-proxy:1.26.2
container_name: socket-proxy
environment:
- CONTAINERS=1
- EVENTS=1
volumes:
- /var/run/docker.sock:/var/run/docker.sock:ro
networks:
- docker-proxynet
restart: always
read_only: true
tmpfs:
- /run
networks:
proxy:
external: true
docker-proxynet:
internal: true