Skip to content

docs: clarify Windows Docker Desktop UDP troubleshooting#413

Closed
txhno wants to merge 9 commits into
ruvnet:mainfrom
txhno:docs/windows-docker-udp-troubleshooting
Closed

docs: clarify Windows Docker Desktop UDP troubleshooting#413
txhno wants to merge 9 commits into
ruvnet:mainfrom
txhno:docs/windows-docker-udp-troubleshooting

Conversation

@txhno

@txhno txhno commented Apr 22, 2026

Copy link
Copy Markdown

Summary

  • add a Windows-specific troubleshooting entry for Docker Desktop multi-source UDP behavior
  • document the maintainer-endorsed relay/port-mapping workaround for ESP32 multi-node setups
  • update the user guide to point Windows users at the new troubleshooting guidance instead of recommending unsupported host networking

Validation

  • git diff --check
  • reviewed the updated markdown sections locally for links, formatting, and wording

ruvnet added a commit that referenced this pull request May 17, 2026
…ws (#502)

Docker Desktop on Windows demultiplexes inbound UDP from multiple source
IPs onto a single virtual socket, silently dropping packets from all but
one ESP32 node. This makes multi-node sensing setups appear to work
(WebSocket connects, packets flow on the host) while only one node's CSI
ever reaches the container.

Adds scripts/udp-relay.py (stdlib only) which collapses multi-source UDP
to a single loopback source so Docker's forwarding accepts every packet.
Verified locally: 6 packets from 3 distinct source ports all arrive at
the receiver from a single relay socket.

Updates docker/docker-compose.yml with an inline comment pointing
Windows users at the relay + 5006:5005 mapping. Linux/macOS hosts are
unaffected and need no changes.

Also documents the workaround alongside fixes for #188 (UI 404 from
relative --ui-path) and #438 (boot loop on --edge-tier 1/2 against
pre-v0.4.3.1 firmware) as new sections 9-11 of docs/TROUBLESHOOTING.md.
Supersedes the docs-only PR #413.

Closes #374, #386
Refs #188, #438, #301
@ruvnet ruvnet closed this in #502 May 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants