Can't run docker in esp32 mode

[xixixihaha]

I pull the latest image according to the guide by using: docker pull ruvnet/wifi-densepose:latest
When I execute the command:
docker run -p 3000:3000 -p 3001:3001 -p 5005:5005/udp ruvnet/wifi-densepose:latest --source esp32
to connect the ESPs, I got the following error.
/bin/sh: 0: Illegal option --

I've tried on both Windows and Linux and got the same result.

[ruvnet]

Thanks for reporting this! The error makes sense — here's what's happening and how to fix it.

The Problem

The Docker image uses an environment variable (CSI_SOURCE) to select the data source, not a command-line flag. When you append --source esp32 to docker run, Docker interprets it as a replacement for the container's CMD, which breaks the shell entrypoint.

The Fix

Use the -e flag to set the environment variable instead:

docker run -p 3000:3000 -p 3001:3001 -p 5005:5005/udp \
  -e CSI_SOURCE=esp32 \
  ruvnet/wifi-densepose:latest

Available source modes

Value	Description
auto	Probe UDP:5005 for ESP32, fall back to simulation (default)
esp32	Require real ESP32 CSI frames on UDP:5005
simulated	Synthetic data, no hardware needed

ESP32 UDP Setup

Make sure your ESP32 nodes are sending CSI frames to the Docker host's IP on port 5005. The -p 5005:5005/udp mapping forwards UDP traffic into the container.

If you're on Windows with Docker Desktop, the ESP32 should target your machine's LAN IP (not localhost), since Docker Desktop uses a Linux VM.

Note

The auto mode (default) already checks for ESP32 on UDP:5005 first and falls back to simulated data if nothing is found — so in most cases you can just run:

docker run -p 3000:3000 -p 3001:3001 -p 5005:5005/udp ruvnet/wifi-densepose:latest

and it will auto-detect your ESP32 if it's sending frames.