w11 host v0.4.0 crashes

[sabey]

hi, I just had a few of my w11 hosts update and it seems they're consistently broken but my linux hosts are fine

I'm not sure what to do exactly, but I thought I should post my log and rollback in the meantime.

[NOTICE]   (1) : Initializing new worker (12)
[NOTICE]   (12) : haproxy version is 3.2.4-98813a1
[WARNING]  (12) : missing timeouts for backend 'docker-events'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[NOTICE]   (12) : config: Can't open global server state file '/var/lib/haproxy/server-state': No such file or directory
[NOTICE]   (1) : Loading success.
HAProxy version 3.2.4-98813a1 2025/08/13 - https://haproxy.org/
[NOTICE]   (1) : haproxy version is 3.2.4-98813a1
Status: long-term supported branch - will stop receiving fixes around Q2 2030.
[ALERT]    (1) : Current worker (12) exited with code 132 (Illegal instruction)
Known bugs: http://www.haproxy.org/bugs/bugs-3.2.4.html
[WARNING]  (1) : A worker process unexpectedly died and this can only be explained by a bug in haproxy or its dependencies.
Running on: Linux 6.6.87.2-microsoft-standard-WSL2 #1 SMP PREEMPT_DYNAMIC Thu Jun  5 18:30:46 UTC 2025 x86_64
Please check that you are running an up to date and maintained version of haproxy and open a bug report.
[ALERT]    (1) : exit-on-failure: killing every processes with SIGTERM
[WARNING]  (1) : All workers exited. Exiting... (132)

[josep-tecnativa]

Hi, thanks for reporting 🙏.
Sorry I can’t test this myself since I don’t use Windows.

I would say that this image only works with Linux containers mode in Docker Desktop (via WSL2), where the Unix socket /var/run/docker.sock exists.
If you're running Windows containers, the proxy crashes because there’s no Unix socket-only a Windows named pipe, which the proxy doesn't support.
The recommended fix is switching Docker Desktop to Linux containers.

Maybe @Programmer-Admin also has some insight, since opened the related PR.

Let me know if switching fixes it!

[sabey]

I'll try to look into it more but I believe I'm already using that. My current docker-compose which I share between linux/w11 does use docker.sock and works as of v0.3.0 - as in the socket is avaliable in wsl and seems to work.

services:
  docker-socket-proxy:
    container_name: docker-socket-proxy
    image: tecnativa/docker-socket-proxy:0.3
    restart: always
    volumes:
      - "/var/run/docker.sock:/var/run/docker.sock:ro"
    ports:
      - 0.0.0.0:2375:2375

[Programmer-Admin]

Hello @sabey - @josep-tecnativa was right, I infact have tested it on Windows with Linux Containers, it does work. Since I set to use LX containers as default, I didn't tested it with Windows Containers. But yeah, lemme know if switching fixes the issue!

[sabey]

I am using Linux Containers not Windows Containers and it does not work.

[Programmer-Admin]

@sabey - It's working with Linux Containers on my machine. Here goes my spec:

Command :

wsl --version

Output:

WSL version: 2.5.10.0
Kernel version: 6.6.87.2-1
WSLg version: 1.0.66
MSRDC version: 1.2.6074
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.26100.4946

Command :

docker container run -d --privileged  --name dockerproxy -v /var/run/docker.sock:/var/run/docker.sock -p 127.0.0.1:2375:2375 ghcr.io/tecnativa/docker-socket-proxy

Output :

Unable to find image 'ghcr.io/tecnativa/docker-socket-proxy:latest' locally
latest: Pulling from tecnativa/docker-socket-proxy
Digest: sha256:44538370af9103858aa387860f355bed72e7f4e15380ef829b53ed4e154cedcd
Status: Downloaded newer image for ghcr.io/tecnativa/docker-socket-proxy:latest
e759aa5002b0e9b9387932d72dd802e6ec3e6642a3e8aad8c4ee8bdf6d191a05

Command : set DOCKER_HOST=tcp://localhost:2375
Command : docker version

Output:

Client:
 Version:           28.3.2
 API version:       1.51
 Go version:        go1.24.5
 Git commit:        578ccf6
 Built:             Wed Jul  9 16:12:31 2025
 OS/Arch:           windows/amd64
 Context:           default

Server: Docker Desktop 4.44.3 (202357)
 Engine:
  Version:          28.3.2
  API version:      1.51 (minimum version 1.24)
  Go version:       go1.24.5
  Git commit:       e77ff99
  Built:            Wed Jul  9 16:13:55 2025
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.7.27
  GitCommit:        05044ec0a9a75232cad458027ca83437aae3f4da
 runc:
  Version:          1.2.5
  GitCommit:        v1.2.5-0-g59923ef
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

Command: docker ps

Output:

Error response from daemon: <html><body><h1>403 Forbidden</h1>
Request forbidden by administrative rules.
</body></html>

On a separate command prompt session, tried to see the logs of the docker-socket-proxy container.

Command: docker logs -f dockerproxy

Output:

[NOTICE]   (1) : Initializing new worker (12)
[NOTICE]   (12) : haproxy version is 3.2.4-98813a1
[WARNING]  (12) : missing timeouts for backend 'docker-events'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[NOTICE]   (12) : config: Can't open global server state file '/var/lib/haproxy/server-state': No such file or directory
[NOTICE]   (1) : Loading success.
::ffff:172.17.0.1:43166 [29/Aug/2025:02:56:52.886] dockerfrontend dockerbackend/dockersocket 0/0/0/5/5 200 272 - - ---- 1/1/0/0/0 0/0 "HEAD /_ping HTTP/1.1"
::ffff:172.17.0.1:43166 [29/Aug/2025:02:56:52.892] dockerfrontend dockerbackend/dockersocket 0/0/0/12/13 200 1054 - - ---- 1/1/0/0/0 0/0 "GET /v1.51/version HTTP/1.1"
::ffff:172.17.0.1:43182 [29/Aug/2025:02:56:57.023] dockerfrontend dockerbackend/dockersocket 0/0/0/4/4 200 272 - - ---- 1/1/0/0/0 0/0 "HEAD /_ping HTTP/1.1"
::ffff:172.17.0.1:43182 [29/Aug/2025:02:56:57.028] dockerfrontend dockerfrontend/<NOSRV> 0/-1/-1/-1/0 403 192 - - PR-- 1/1/0/0/0 0/0 "GET /v1.51/containers/json HTTP/1.1"
::ffff:172.17.0.1:56894 [29/Aug/2025:02:58:25.675] dockerfrontend dockerbackend/dockersocket 0/0/0/9/9 200 272 - - ---- 1/1/0/0/0 0/0 "HEAD /_ping HTTP/1.1"
::ffff:172.17.0.1:56894 [29/Aug/2025:02:58:25.687] dockerfrontend dockerfrontend/<NOSRV> 0/-1/-1/-1/0 403 192 - - PR-- 1/1/0/0/0 0/0 "GET /v1.51/containers/json HTTP/1.1"

[TheGITofTeo997]

Getting the same issue on my NAS as described in #160

[sabey]

I recommend this solution below as hasproxy is still broken and if you update Docker they've bumped up the required api version (DOCKER_API_VERSION).

#123 (comment)
https://github.com/Qtax/docker-socket-proxy