I'm currently working on a project using ESP32-S3 boards to detect human presence over WiFi, and I'm utilizing the ruvnet/wifi-densepose Docker image for this. My setup includes two ESP32-S3-WROOM-1 boards and I'm running Docker Desktop with WSL2 on Windows 11. I'm encountering a problem where my ESP32 RX board is sending CSI data via UDP to my laptop's IP (192.168.137.1:5005), but for some reason, the Docker container isn't receiving any data. The Docker logs indicate no incoming CSI frames, despite confirming that the port mapping is correct, the Python script shows data is being sent, and netstat confirms that UDP port 5005 is open. I've tried several troubleshooting steps, such as setting up portproxy (which doesn't work for UDP), creating a Python bridge, sending data to the container's IP directly, using the --network host flag, and adding firewall rules. There's an interesting note that this setup worked once before, albeit with the wrong port mapping. I'm curious if there's a known issue with UDP port forwarding in Docker Desktop on Windows with WSL2 enabled, and if anyone has a workaround to help receive those UDP packets in the Docker container.
2 Answers
It sounds like Docker could be causing the issue. Have you checked the Docker network settings? Sometimes, using a pure Python implementation to receive UDP might save you a lot of headaches. You could bypass Docker for now and see if you can get the data flowing directly into Python.
Have you considered simplifying your setup for troubleshooting? Try running netcat instead of using the ESP32 or Docker, just to see if you can send and receive data. This might help isolate the issue.
That's a great suggestion! I tried using Wireshark to monitor the traffic, but it doesn't show anything when I send UDP to 127.0.0.1:5005. It's looking like Docker might be blocking loopback UDP entirely.
I agree! Working with just Python might simplify things until you can pinpoint what's going wrong with Docker. It can be frustrating to diagnose network issues like this.