It's a floating bug for 5.1.X and 6.0. It's just the fact that sometimes dnat rules from Docker don't get applied. It can be fixed by restarting container, but it is very rare and happens mostly just in virtual environments. This is already fixed in 6.1 with host networking feature.
It's a floating bug for 5.1.X and 6.0. It's just the fact that sometimes dnat rules from Docker don't get applied. It can be fixed by restarting container, but it is very rare and happens mostly just in virtual environments. This is already fixed in 6.1 with host networking feature.