kelin/EZ-Homelab
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: resolve dockerproxy port 2375 conflict

Browse Source 
- Remove port mapping from dockerproxy service
- Docker daemon already provides TCP API access on port 2375
- dockerproxy runs for security but doesn't expose conflicting port
- Resolves 'port already allocated' error during deployment
This commit is contained in:
EZ-Homelab
2026-01-23 18:29:52 -05:00
parent 28064ff385
commit 3723cebe9c
1 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
docker-compose/infrastructure/docker-compose.yml
View File

@@ -26,12 +26,13 @@ services:
# 2. Firewall must allow access to port 2375 from Sablier service # 2. Firewall must allow access to port 2375 from Sablier service
# 3. Docker daemon config should include: "hosts": ["tcp://0.0.0.0:2375", "unix:///var/run/docker.sock"] # 3. Docker daemon config should include: "hosts": ["tcp://0.0.0.0:2375", "unix:///var/run/docker.sock"]
# 4. For security, consider restricting access to specific IP ranges or using TLS # 4. For security, consider restricting access to specific IP ranges or using TLS
# 5. dockerproxy runs for additional security but doesn't expose port 2375 (handled by Docker daemon)
image: tecnativa/docker-socket-proxy:latest image: tecnativa/docker-socket-proxy:latest
container_name: dockerproxy container_name: dockerproxy
privileged: true privileged: true
restart: unless-stopped restart: unless-stopped
ports: # Note: Port 2375 is handled directly by Docker daemon for Sablier access
- 2375:2375 # dockerproxy provides additional security features but doesn't expose the port
volumes: volumes:
- /var/run/docker.sock:/var/run/docker.sock - /var/run/docker.sock:/var/run/docker.sock
environment: environment: