Cool, that sounds slightly more positive than the latest reply I got to my ticket, which was basically just, "we've reproduced the issue, but have no ETA on a fix". 
I'm cautiously optimistic. āAs soon as possibleā could be tomorrow or months from now. But at least they confirm there is an issue and I'm not hallucinating. It's a win - win in that regard. 
1 Like
Woke up to this today:
Hello,
This is an automated message. Our bug tracker reports that your issue has been fixed. This means that we plan to release a RouterOS update with this fix. Make sure to upgrade to the next release when it comes out.
Assume 7.21.3 might be coming out sooner than later.
1 Like
Oh no, that isnāt certain at all! This message only means that the issue has been fixed in their development version and it can be that it appears only in 7.22 or even 7.23.
Fixed in 7.22rc1
Thereās a new `hosts` arguments to containers, what is it useful for and how should it be used.
I initially thought itās about local port(s) vs container port(s) but then why the second field requires an IP? I tried multiple combination but I donāt see any changeā¦
Wow, good catch, thanks!
I expected to be able to map container ports to local ports on different ones.
Maybe it's something for DSTNAT, or in case of HTTP/HTTPS, the new IP -> Reverse Proxy feature in 7.22?
Yup DNAT works, that's enough for now. I'll check the reverse proxy whenever it's released, I hadn't read about it yet, thanks!