3 ms·
Except it is not clear at all and should mention the firewall changes. I expect that publishing means listening on 0.0.0.0, not messing with the firewall.
by allarm 4y ago
Except it is not clear at all and should mention the firewall changes. I expect that publishing means listening on 0.0.0.0, not messing with the firewall.
- selfmodruntime 4y agoSee my comment above. Firewall changes are clearly mentioned under the section "published ports". What you expect does not matter. What you're thinking of is exposing. It's even in the word "publish". The documentation has two sections entirely devoted to the terms. It's in the section "container networking", which is marked as required reading by the docs. It's not dockers fault that you're copy pasting configuration examples from medium blogs. [0]: https://docs.docker.com/config/containers/container-networking/#published-ports https://docs.docker.com/config/containers/container-networki...
- allarm 4y agoYou know, it would be nice for you to actually read the docs before posting insulting comments. > This creates a firewall rule in the container We’re done here.