There are bigger ARM routers in the MikroTik line such as the CCR2116, but if you can justify a CCR, you're unlikely to be able to justify soaking up its considerable specialized power by running flabby containers on it.

To even get the container running at all, you'll be motivated to select the most pared-back sort of containers.Įven a biggish home router like the RB5009 is only about as powerful as a Raspberry Pi 4, and it has plenty of other stuff to do in the background besides running your containers. For the most part, containers are only sensible on the higher-end ARM-based MikroTik routers due to assorted limitations I cover elsewhere. Containers are nearly a joke on most of MikroTik's ARM-based switches, since none of them offer external storage options, as of this writing. If you can shell in at all, it'll operate more like single-user mode in the classical Unix sense than anything else.ĬHR aside, running containers on RouterOS implies use of MikroTik ARM hardware, most of which is rather low-spec. It won't even be running a multi-user pseudo-tty login daemon. Indeed, it's possible to pare a container down to a single executable that runs atop the host kernel, offering no other services.Įven when you deploy a single-purpose service atop a base image derived from a full Linux OS such as Ubuntu or Alpine, it won't be running SSH or a GUI, and it won't have any kind of background service daemon.

no procps, or a stripped-down minimalist alternative.

no root user, or at least one well and truly nerfed.

With a container, it's possible that it has… Even when you start with a stripped-down host OS, the resulting VM is likely to have all the features of an old-school Unix server at the least, and likely much more besides. The creation of a classic virtual machine starts with installing a fully-featured host OS, then installing one or more applications atop that.

Mikrotik chr kvm