I’m seeing a few unhappy comments about this, so I’ll just point out a couple of things:<p>1. This was introduced in a beta. It was then removed from subsequent betas until a fix could be found.<p>2. Running docker on a router could be really helpful in some cases, especially for small ISPs such as mine. For example: being able to run a recursive DNS resolver at the broadcast tower (ie nearer the customer) without having to run an entire server would be great. Or running a Prometheus exporter on the router for metric collection. Or for local processing/archiving of netflow data.<p>There are some really helpful use cases for this, but they are not the normal devops reasons for using docker.
This is seriously the last straw for me, I'll be switching away from Mikrotik to OpenWRT devices, a router should stay a router, not run containers!<p>The attack area on a router should shrink, not grow!
Oh boy, glad I moved mine to SwitchOS I guess. This being a beta means I would've ended up with this eventually, and Docker is just not something I want on a network device<p>Seriously considering replacing this with Mikrotik showing up so often<p>Edit: Any recommendations for 10GbE switches with ~8 ports would be appreciated, likely encouraging me to follow through