Is there an existing issue for this?
Current Behavior
Recently all machines using linuxserver docker proxy updated, to 3.4.4 and I lost logging access withing my Dockhand container.
Rolled back to 3.4.1-r0-ls87 and all is again well.
Hopefully others smarter than I have shared a similar.
Expected Behavior
Full logging functionality on apps connected via socket-proxy
Steps To Reproduce
Start Dockhand.
Select container logs
Keeps trying to connect. Fails.
Environment
- OS: Trixie
- How docker service was installed: Using Docker 29.7.2 from docker repo.
Docker creation
services:
socket-proxy:
image: lscr.io/linuxserver/socket-proxy:latest
container_name: socket-proxy
restart: unless-stopped
networks:
- socket_proxy
environment:
## Granted by Default
- EVENTS=1 # Container event monitoring
- PING=1 # Health checks
- VERSION=1 # Docker version info
## Revoked by Default
# Security critical
- AUTH=0 # Authentication APIs, Portainer per Copilot
- SECRETS=0 # Docker secrets access
- POST=1 # Required for create/update operations
# Not always needed
- ALLOW_START=1 # Dockge, Dockpeek,
- ALLOW_STOP=1 # Dockge, Dockpeek,
- ALLOW_RESTARTS=1 # Dockge, Dockpeek,
- BUILD=0 # optional
- COMMIT=0 # Container commits
- CONFIGS=0 # Docker configs
- CONTAINERS=1 # Container management
- DF=1 # size data per dockhand
- DISABLE_IPV6=1 # optional
- DISTRIBUTION=0 # Distribution APIs
- EXEC=1 # Execute commands in containers
- IMAGES=1 # Image building
- INFO=1 # Docker system info
- NETWORKS=1 # Network management
- NODES=0 # Node management
- PLUGINS=0 # Plugin management
- PROXY_READ_TIMEOUT=240 #optional
- SERVICES=0 # Service management (Swarm), Portainer
- SESSION=0 # Session management
- SWARM=0 # Docker Swarm features
- SYSTEM=1 # System-wide operations, not for arcane
- TASKS=0 # Task management (Swarm), Portainer
- VOLUMES=1 # Volume management
volumes:
- /var/run/docker.sock:/var/run/docker.sock:ro
read_only: true
tmpfs:
- /run
networks:
socket_proxy:
external: true
Container logs
Is there an existing issue for this?
Current Behavior
Recently all machines using linuxserver docker proxy updated, to 3.4.4 and I lost logging access withing my Dockhand container.
Rolled back to 3.4.1-r0-ls87 and all is again well.
Hopefully others smarter than I have shared a similar.
Expected Behavior
Full logging functionality on apps connected via socket-proxy
Steps To Reproduce
Start Dockhand.
Select container logs
Keeps trying to connect. Fails.
Environment
Docker creation
services: socket-proxy: image: lscr.io/linuxserver/socket-proxy:latest container_name: socket-proxy restart: unless-stopped networks: - socket_proxy environment: ## Granted by Default - EVENTS=1 # Container event monitoring - PING=1 # Health checks - VERSION=1 # Docker version info ## Revoked by Default # Security critical - AUTH=0 # Authentication APIs, Portainer per Copilot - SECRETS=0 # Docker secrets access - POST=1 # Required for create/update operations # Not always needed - ALLOW_START=1 # Dockge, Dockpeek, - ALLOW_STOP=1 # Dockge, Dockpeek, - ALLOW_RESTARTS=1 # Dockge, Dockpeek, - BUILD=0 # optional - COMMIT=0 # Container commits - CONFIGS=0 # Docker configs - CONTAINERS=1 # Container management - DF=1 # size data per dockhand - DISABLE_IPV6=1 # optional - DISTRIBUTION=0 # Distribution APIs - EXEC=1 # Execute commands in containers - IMAGES=1 # Image building - INFO=1 # Docker system info - NETWORKS=1 # Network management - NODES=0 # Node management - PLUGINS=0 # Plugin management - PROXY_READ_TIMEOUT=240 #optional - SERVICES=0 # Service management (Swarm), Portainer - SESSION=0 # Session management - SWARM=0 # Docker Swarm features - SYSTEM=1 # System-wide operations, not for arcane - TASKS=0 # Task management (Swarm), Portainer - VOLUMES=1 # Volume management volumes: - /var/run/docker.sock:/var/run/docker.sock:ro read_only: true tmpfs: - /run networks: socket_proxy: external: trueContainer logs