Run a container Worker
Choose the MDK container Worker guide for your hardware.
Overview
MDK drives each container system through its own Worker. These guides are task-focused and independent, you only need the one for the hardware you operate.
If Kernel, Worker, manager, or thing are unfamiliar, read terminology first.
Pick your hardware
The authoritative model list for every Worker is the generated supported-hardware catalogue. Covered so far:
Prerequisites
Every guide assumes:
- Node.js >=24 (LTS)
- npm >=11
- Commands are run from the repo root
- Outbound network access for Kernel discovery
For the mock or development path:
- No physical container is required
- The runnable example for your model starts the bundled mock and registers it
HRPC relies on HyperDHT for peer connectivity. Use the network requirements and checks if an example stalls before printing the Kernel key.
For the deployment path:
- A Node.js service or script in your deployment that runs the MDK Worker and registers devices
- A supported container system reachable from the machine or container running the Worker
- The Worker's README for the exact
registerThingoptions
Next steps
- Browse supported hardware
- New to the moving parts? Read terminology (Kernel, Worker, manager, thing, mock)
- If an example does not start or a mock port is busy, use miner troubleshooting, the same HRPC and DHT checks apply
- Drive the registered device from the CLI or dashboard: Get started