routeros-containerlisted

# RouterOS Container Subsystem ## Overview RouterOS 7.x includes a container subsystem (`/container`) that runs OCI-compatible container images directly on MikroTik hardware. It is NOT Docker — it's MikroTik's own implementation with significant differences. **Requirements:** - RouterOS 7.x with `container` extra package installed - Device-mode must be enabled (requires physical access for initial setup) - Sufficient storage (external USB disk recommended, 100+ MB/s, 10K+ random IOPS) - ARM, ARM64, or x86 architecture (MIPS not supported for containers) ## Device-Mode — Physical Access Required Container support is gated behind device-mode, which requires physical confirmation (reset button press or power cycle) to enable: ```routeros # Enable container mode /system/device-mode/update mode=advanced container=yes # After executing: physically confirm within activation-timeout # - Press reset button, OR # - Power cycle the device ``` Device-mode is a general RouterOS security feature — not container-specific. It gates many features (scheduler, fetch, sniffer, etc.) across four modes (`home`, `basic`, `advanced`, `rose`) with device-dependent factory defaults. For the full feature matrix, modes, update properties, and physical confirmation details: see the [Device-mode reference](../routeros-fundamentals/references/device-mode.md) in the `routeros-fundamentals` skill. **Mode script bypass (7.22+):** During netinstall, a mode script (`-sm`) can set device-mode on first