You have no items in your shopping cart.
Menu

Containerized App Management with RouterOS by MikroTik

Containerized Application Management with MikroTik RouterOS Apps

Deploy infrastructure services directly on RouterOS using integrated containerized applications.

Beginning with RouterOS v7.21, MikroTik introduced the Apps menu within WinBox and RouterOS. This feature provides a simplified method for deploying containerized applications directly on supported MikroTik platforms.

Applications included in the catalog contain preconfigured containers along with required RouterOS configuration such as firewall policies, NAT rules, and networking integration. In most deployments, enabling an application is all that is required for it to begin operating successfully.

Platform Improvements in RouterOS v7.22

RouterOS v7.22 release candidates introduced additional networking flexibility by allowing VLAN tagging directly on the bridge interface used by applications.

While advanced deployments may benefit from this capability, most installations function immediately using default networking. In production environments we currently operate multiple applications including Technitium DNS across both office and home networks.

Available Applications

At the time of writing, more than 80 applications are available through the RouterOS catalog across multiple categories.

Productivity Platforms:

  • PartDB
  • Wallabag
  • WordPress
  • AdventureLog

Media Management:

  • Jellyfin
  • Plex
  • Sonarr
  • Jackett

ISP and Engineering Tools:

  • code-server
  • Livebook
  • SmokePing
  • Speedketchup
  • Zabbix

Additional services include databases, Elasticsearch, Home Assistant, Vaultwarden, Roundcube, and many others available directly within WinBox.

Hardware Requirements

RouterOS Apps currently require platforms supporting container workloads including:

  • x86 RouterOS systems
  • ARM64-based MikroTik platforms

Recommended deployment platforms:

  • CCR2116
  • CCR2216
  • RDS systems

Fast storage is strongly recommended. NVMe drives significantly improve container startup and runtime performance.

Enabling Container Device Mode

Container functionality requires enabling device mode with physical access to the router. 

/system/device-mode update container=yes

After issuing the command, reboot the router using power cycling or the reset/mode button within five minutes to activate container support.

Preparing Storage

Once NVMe storage is installed, format the disk under System → Disks.

  • Filesystem: ext4
  • Example mount point: nvme1

This disk will be assigned as the application storage location within App Setup.

Deploying an Application

Deploying applications is intentionally simple.

  1. Select the desired application.
  2. Click Enable.

RouterOS automatically downloads and launches the container while applying required networking rules.

Applications may run on internal container networks with NAT or directly on the LAN bridge depending on configuration preference.

Application Lifecycle Management

  • Disable — Stops the container while preserving configuration.
  • Cleanup — Removes the application and all stored data.
  • Update — Downloads and applies the latest container version automatically.

Operational Experience

In production testing, RouterOS Apps have required minimal system resources. A CCR2116 with 16GB RAM continues to maintain significant available memory even while running multiple applications.

Services such as Technitium DNS, Speedketchup monitoring, Uptime Kuma, and logging platforms start quickly and operate reliably without requiring separate virtualization infrastructure.

Final Thoughts

RouterOS Apps bridge the gap between modern containerized services and network infrastructure. For operators already deploying MikroTik platforms, this provides an efficient way to host monitoring, DNS, logging, and operational tooling directly within the routing environment.

Leave your comment

*