Socket proxy

[jei1965]

I am trying to setup Hawser on a host. The host has a socket-proxy stack that is connect to an external network called proxy-network. I setup the hawser compose file with DOCKER_HOST=tcp://socket-proxy:2375. Whenever I try to start the hawser stack I get DOCKER_HOST=/var/lib/docker.sock and it can't find the docker host and exits

Here is my docker-compose and .env file

`services:
socket-proxy:
image: lscr.io/linuxserver/socket-proxy:latest
container_name: socket-proxy-hawser
restart: unless-stopped
volumes:
- /var/run/docker.sock:/var/run/docker.sock:ro
env_file:
- .env
networks:
- socket-internal

hawser:
image: ghcr.io/finsys/hawser:latest
container_name: hawser
depends_on:
- socket-proxy
environment:
- TOKEN=${HAWSER_TOKEN}
- DOCKER_HOST=tcp://socket-proxy:2375
volumes:
- ./hawser_data:/data/stacks
networks:
- socket-internal
- ha-server

networks:
socket-internal:
name: socket-internal
internal: true
ha-server:
name: ha-server
external: true`

.env file sanitized
`# socket-proxy permissions

LOG_LEVEL=warning #option
CONTAINERS=1 #optional
IMAGES=1 #optional
INFO=0 #optional
NETWORKS=1 #optional
PING=1 #optional
POST=1 #optional
VOLUMES=1
DELETE=0
BUILD=0`

# hawser token HAWSER_TOKEN=token

When I run it I get
✔ Container socket-proxy-hawser Running 0.0s Attaching to hawser, socket-proxy-hawser hawser | ╭─────────────────────────────────────╮ hawser | │ HAWSER AGENT │ hawser | │ Remote Docker Agent for │ hawser | │ Dockhand │ hawser | ╰─────────────────────────────────────╯ hawser | Version: 0.2.29 (eb7d4b7) hawser | Agent ID: d3e4c898-5171-4758-958f-73dabdae519d hawser | Agent Name: d8dfcea400af hawser | Docker Socket: /var/run/docker.sock hawser | Log Level: INFO hawser | hawser | 2026/02/28 00:13:09 [INFO] Starting in Standard mode on port 2376 hawser | 2026/02/28 00:13:09 [ERROR] Error: failed to create Docker client: failed to connect to Docker: Get "http://localhost/_ping": dial unix /var/run/docker.sock: connect: no such file or directory hawser exited with code 1

Any help with getting this running would be appreciated

Thanks

[IMNotMax]

Same here, looks like the socket is hard coded
I know Portainer can have a command to pass the socket address (like -H tcp://socket-proxy:2375 ).
Wish Hawser and Dockhand will one day !

Another issue on the same spot : #44

[IMNotMax]

With some research, I learned how docker tcp socket can work.
With this doc and help from my favorite LLM, I manage to set http with TLS (HTTPS) from dockhand to my distant machine. No need to add hawser.
Not a solution to use local socket proxy but -1 container and Dockhand uses a secured connexion with TLS.
Dockhand as a direct access to the local machine, no real issue to give direct access to remote machines.

socket-proxy will be used for other remote containers if needed.