Docker

Choosing an image

Image	Notes
emqx/neuronex:x.y.z	Standard image. Includes the Python runtime and the rules engine Python SDK (ekuiper, pynng). Required for Python portable plugins
emqx/neuronex:x.y.z-extend	Based on the standard image, with additional FFmpeg and ONNX dependencies

When in doubt, use the standard image. The full tag list is on Docker Hub, and images are also linked from the download page.

Starting the container

docker pull emqx/neuronex:3.9.2

docker run -d --name neuronex \
  -p 8085:8085 \
  -v /host/neuronex-data:/opt/neuronex/data \
  --ulimit nofile=65535:65535 \
  --log-opt max-size=100m \
  --privileged=true \
  emqx/neuronex:3.9.2

Open http://localhost:8085 and sign in with the default account admin / 0000.

The data directory must be mounted

-v maps a host directory onto the container's /opt/neuronex/data. Without it, removing the container also destroys your driver configuration, tag lists, and rules.

Runtime options

Option	Purpose
-p 8085:8085	Port mapping for the web console and the HTTP API
-v <host dir>:/opt/neuronex/data	Persist configuration and data — see the warning above
--ulimit nofile=65535:65535	Raise the file descriptor limit; needed with many nodes, see below
--log-opt max-size=100m	Cap the size of the container's stdout log
--privileged=true	Run the container in privileged mode; included in the default commands
--restart=always	Restart the container automatically when the Docker daemon restarts
--device <host device>:<container device>	Map a serial port or other device, see Connecting serial devices

For more startup parameters, see Startup Parameters and Configuration File.

Connecting serial devices

To collect over serial protocols such as Modbus RTU or DL/T645, map the host's serial port into the container:

docker run -d --name neuronex \
  -p 8085:8085 \
  --device /dev/ttyUSB0:/dev/ttyS0 \
  --privileged=true \
  emqx/neuronex:3.9.2

/dev/ttyUSB0 is the device on the host and /dev/ttyS0 is its path inside the container — use the container path in the driver's serial device parameter. Repeat --device for each additional port.

Raising the file descriptor limit for larger deployments

Every running node consumes a number of file descriptors. With many nodes configured, the total exceeds the container's default limit of 1024, which shows up as nodes failing to connect or disconnecting repeatedly.

The direct fix is to raise the limit:

--ulimit nofile=65535:65535

The default startup commands include --privileged=true, which lifts the container's restrictions including the descriptor limit. It also grants the container privileges close to host root. In a hardened deployment, remove that parameter and keep --ulimit when raising the descriptor limit is all that is required.

Uninstalling

Stop and remove the container:

docker stop neuronex || true
docker rm neuronex || true

To remove the image as well:

docker rmi emqx/neuronex:<tag>

TIP

If you mounted a host directory with -v, removing the container leaves that data in place. Delete the directory yourself if you no longer need it.