No, you're right: the current RouterOS docs on containers positively suck compared to what you get for other container platforms. Your next-best option is SSHing into a box running the containers.npk package, typing "/container", and then pressing the F1 and Tab keys a lot. Between that, ...

Yeah I made the same wrong assumption some time ago. And with the different vETH's , you have full flexibility with things like DNAT etc if you want to expose to the outside world etc. Curious, is there more detailed documentation other than this page ? I've searched around but I haven't found any ...

That makes sense. I tried implementing this at the time of the original post but I am on a level 1 license that restricts to just 1 VETH interface. I was also thrown off with the documentation's example of using 172.17.0.2/16 which made me think the large IP block is for multiple containers using th...

I'm trying to run unbound container as the upstream DNS resolver for PiHole to use locally instead of remote DNS like 1.1.1.1. I'm not seeing how to do that in the documentation for Containers in ROS Because that is not a part of MT. However, You could change it like any other Linux operation syste...

I was looking into documentation and I didn't see how one would do port mapping with Containers in ROS 7. How did you miss this ? It's precisely the same thing as "docker create --publish 80:80". Then what do you do with two containers both using port 80? They're both on the same VETH.

Container image names are lost when restoring from a configuration backup.

What you wrote is convoluted and not so understandable, try to spend some time translating it better, rather than having fun with the "reports"...

Fair enough.

+1 for OpenWRT minimal container. It's very lightweight and there is already package manager and other good features available for all architectures ROS runs on. Also maybe make minimal containers with just busybox for different architectures. Something that can be easily used for doing scripting o...

I'm trying to run unbound container as the upstream DNS resolver for PiHole to use locally instead of remote DNS like 1.1.1.1 or 8.8.8.8 (for example). Unbound is using port 53 by default and that conflicts with PiHole. Normally, I would do a port mapping for Unbound, for example 5053:53. I'm not se...

Yea I know that and I have seen the script to use. But I'm trying to confirm and understand whether Address List is made to only resolve Mikrotik Cloud DDNS URLs since my custom URL doesn't seem to resolve to my WAN IP. I mentioned this in the first post. I am currently using a Cloudflare service to...

With non-x86 RouterOS, I am able to use IP -> Cloud to get a DDNS address which could be added to the Address List to resolve to my WAN IP. Since Cloud service is not supported in RouterOS 7 x86, how would I go about doing this? I am currently using a Cloudflare service to update a subdomain I with ...