Many of the problems on the list in my article linked above can be solved by switching from piggy services written in scripting languages, with many external dependencies to single statically-linked binaries. Examples: authoritative DNS server, DNS proxy that can integrate static + caching + DoH, etc. To replace a weak service on the router with a better one.Anything that has to happen at the border of a network, where port-forwarding and such won't work.While I do agree that Docker is of limited use on RouterOS, there are broad cases where it'll be worth putting up with the many problems you buy in using the feature: Automatically disable Internet and Wifi at the end of the Class or at the end of the day. Activate Internet for all or some computers Teacher connected to the Classroom-Network opens the webbrowser and log-in to the server. School could have a small Web-Server installed on the Classroom-Router or switch. Change basic setting like WLAN-Password, SSID, etc. ISP could have a small Web-Server installed on Client devices. Installing Dockers on my Router could be a very nice solution.

My handfull of devices usually make each 1 SQL-Request a day.

I for exemple need at home very small MariaDB-Server for a software I use (Devolutions RDM). Like ioT-Server, Web-Server, Data and Logging, Authentication (freeradius), DNS (pihole) etc. I know a lot of IT-Enthusiast wo use RPi's at home as some sort of low performance Server. There is always a small Feature or Service from the All-in-One Router that Mikrotik can't provide. I find it difficult sometimes to implement a Mikrotik-Routers in a SOHO or SME's environment. So the Docker-Feature is a welcome Tool for my Toolbox I use Mikrotik-Devices all the time to solve problem no other Router can ! In other words, no Entreprise with On-Site virtualization capability, will move there DNS-Server to a Mikrotik-Device! I don't think the Docker-Feature will be widely used in the 'Entreprise' enviroment.

Mikrotik routeros virtualbox