PLEASE MikroTik made NetInstall version for Docker…
I will work on one this weekend sometime and put in my GitHub registry
FANTASTIC!!!
meh. After playing around with it, using a docker image to flash would take more effort than it's worth. You would have to mount the update file in the container and set env vars for the flags. It's way more efficient to just run the binary. If they had a web interface for the linux binary or if someone could write one, that would be the game changer though.
… 
rextended, you have unravelled most of the mysteries in the universe, surely one small docker container is within your skill set!
perhaps jr0dd can be convinced to do so for a bottle of red italian wine!!
I do not have any experience on Docker… sorry 
I am also trying to create such a solution and will be sure to update here when we get it working
I work with docker for years.
But please enlighten me: what/which use-case do we try to solve here? I don’t get it. Running Windows Netinstall binary inside a Linux Docker container. What is this?
Who said Windows netinstall binary? There has been a Linux netinstall version for months now. I think they wish to run the Linux netinstall binary in a docker container.
How will you use it? Is there a use case scenario, where you need to reinstall many devices, but have no Linux or Windows computers anywhere?
Yes. MDU with multiple customers, we have a router on the same broadcast domain. Can reset them all easily without having to travel to site
Remote locations, kilometers away.
It’s not for ‘many devices’, but for that one device once every few years that needs to be netinstalled without having to drive 2 hours to a mountain somewhere.
Use case for us would be where a user 1000km away reboots their router while it is upgrading to a new RouterOS version, now it can no longer boot except to ethernet. We try to create a layer 2 tunnel to the user to netinstall their router when this happens but due to congestion long distance netinstall does not work properly.
E-X-A-C-T-L-Y
NetInstall is more sicure than upgrade, and can clean all what must not be present, if something has happen on “remote” past…
How do you put them into netinstall, mode, if you have no access?
Are they all set by default to nand-if-fail-then-ethernet ?
Yes, they all are, in our case. It seems to be set to this by default. Some of them we can successfully netinstall remotely, if there is enough bandwidth. Others time out because the connection is too slow. It doesn’t happen very often that we have to do this, but would be a handy feature for when this does need to happen.
I have all device powered from 8P, 16P or 24P RouterBOARDs,
on default I set all device
/partitions set [find] fallback-to=etherboot
# this is RouterOS default
/sys routerboard settings
set boot-device=nand-if-fail-then-ethernet
But the point is not only to netinstall devices with problems, but netinstall anything…
But still that would not work?
Suppose while upgrading ROS the user/elec fails and the box boots to ethernet, so in a dodgy state.
Why would would you think the “container logic” on that box would be operational in this state ?
I do not fully understand at what level the container-daemons live in ROS, but I’m sure your ROS must be booted up to a certain level for that.
Is logical that is not the only device present on-site…
Is obvious than the netinstall on a container is used to install another machine.
About power failure, is obvious that is it not a domestic case…