Why Do Teltonika Edge Routers Support Docker?
Docker is a platform for packaging and running software in containers. A container bundles an application with all its code, libraries, and dependencies into a single portable unit that runs identically on any compatible system. The container does its job. The router still routes. Neither gets in the way of the other.
| Term | What it means |
|---|---|
| Container | A self-contained application package with everything it needs to run |
| Image | The template used to create a container – pulled from Docker Hub or uploaded manually |
| Docker Hub | Public registry of pre-built container images for thousands of applications |
| Package Manager | Where you install Docker on a Teltonika router – System → Package Manager in RutOS |
| ARM-compatible | Container images must be built for ARM architecture (linux/arm64 or linux/arm/v7) to run on Teltonika hardware |
Why Has Teltonika Added Docker?
Industrial IoT deployments traditionally needed a cellular router for connectivity and a separate gateway or industrial PC for local processing. That means two devices, two power supplies, more wiring, and more to manage remotely. Teltonika’s RUTC-series routers have the CPU, RAM, and flash to run containerised applications alongside the routing stack – one device instead of two.
| Without Docker | With Docker on RUTC |
|---|---|
| Router + separate gateway or industrial PC | One RUTC device handles both |
| Two power inputs, extra wiring | Single power input |
| Separate management for each device | Everything managed via Teltonika RMS |
| More hardware to procure, install, and maintain | Reduced BOM and site complexity |
Which Teltonika Routers Support Docker?
Docker support requires sufficient RAM and flash storage. The following models currently support Docker via the RutOS Package Manager.
| Model | Connectivity | CPU / RAM / Flash | Wi-Fi | SIM | |
|---|---|---|---|---|---|
| RUTC40 | 4G Cat 4 – Global Telit modem, worldwide LTE bands | Dual-core 1.3 GHz 1 GB RAM / 8 GB flash | Wi-Fi 6 dual-band | Dual SIM + eSIM | View → |
| RUTC41 | 4G Cat 4 150 Mbps down / 50 Mbps up | Dual-core 1.3 GHz 1 GB RAM / 8 GB flash | Wi-Fi 6 dual-band | Dual SIM + eSIM (7 profiles) | View → |
| RUTC50 | 5G Sub-6 GHz SA/NSA | Higher-spec CPU Increased RAM / flash | Wi-Fi 6 dual-band | Dual SIM + eSIM | View → |
What Can You Run?
Any application with an ARM-compatible container image that fits within the device’s resource limits. Common workloads in industrial and IoT deployments include the following.
| Application | What it does on the router |
|---|---|
| Protocol conversion | Modbus-to-MQTT bridges, BACnet translators, OPC-UA adapters. Legacy field equipment communicates with cloud platforms without a separate protocol converter. |
| Node-RED | Local logic flows that filter, aggregate, and route data. Trigger actions based on sensor readings or schedules without cloud round-trips. |
| Local MQTT broker | Eclipse Mosquitto creates a local message bus. Device-to-device communication continues if the WAN link fails. The broker stores and forwards when connectivity resumes. |
| Network monitoring | Netdata or Prometheus exporters for real-time system metrics. Pi-hole for DNS-level filtering across every LAN device. Both run independently of RutOS. |
| Custom business logic | Alarm handlers, compliance loggers, webhook processors, local database writers. Containers have network access to LAN devices and cloud services through the router’s interfaces. |
| ML inference | Lightweight anomaly detection and predictive maintenance on sensor streams. Models must be ARM-optimised and inference-only – the hardware is not suited to training workloads. |
How to Set Up Docker on a Teltonika Router
| Step | Action |
|---|---|
| 1 – Install | System → Package Manager → search Docker → Install. Docker runs alongside RutOS as a service without modifying the core firmware. |
| 2 – Expand storage | System → Administration → Storage Memory Expansion. Mount a USB stick before pulling images from Docker Hub. Strongly recommended. |
| 3 – Run containers | Use the WebUI Docker Manager under Services, or via CLI over SSH using standard Docker commands: docker pull, docker run, docker ps, docker logs. |
| 4 – Port access | Network → Firewall → Port Forwards to expose container services to external connections if needed. |
| 5 – Remote management | The router remains fully RMS-managed. Firmware updates, VPN, and configuration all continue normally alongside container operation. |
Limitations to Know Before Deploying
| Limitation | Detail |
|---|---|
| ARM images only | Container images must be built for linux/arm64 or linux/arm/v7. Not every Docker Hub image has an ARM variant – verify before building your deployment around a specific tool. |
| 1 GB shared RAM | RAM is shared between RutOS and all running containers. Use Alpine Linux base images and keep container footprints lean to avoid memory pressure. |
| Flash storage | 8 GB internal flash fills faster than expected when pulling images. Plan for USB storage expansion from the start – add it to your BOM, not as an afterthought. |
| No rootless Docker | Containers run as root on RutOS. Standard for embedded Linux but worth noting for deployments with strict privilege isolation requirements. |
| Firmware compatibility | Check the Teltonika wiki for firmware version compatibility before deploying containers in production. wiki.teltonika-networks.com/view/RUTC40 |
If you need Teltonika Support for your equipment purchased from The Router Store – Please view this Teltonika Support Page.