Tecnativa / Tecnativa/docker-socket-proxy

w11 host v0.4.0 crashes

Open
#158 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
2.8k
Forks
207
PR merge metrics
No merged PRs in 30d

Description

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)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the supplied HAProxy 3.2.4 log and compare the Windows 11/WSL2 hosts with the working Linux hosts after the v0.4.0 update. Determine whether the illegal-instruction crash is reproducible in docker-socket-proxy or in HAProxy or one of its dependencies; done means identifying a project fix or a confirmed upstream cause and workaround.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, linux
Domain
backend, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.