![networking - Why is firewalld allowing public traffic to my non-public ports, bound to Docker containers? - Server Fault networking - Why is firewalld allowing public traffic to my non-public ports, bound to Docker containers? - Server Fault](https://i.stack.imgur.com/ngjJy.png)
networking - Why is firewalld allowing public traffic to my non-public ports, bound to Docker containers? - Server Fault
![Expose daemon on tcp://localhost:2375 without TLS" option works only for the first Docker run · Issue #3163 · docker/for-win · GitHub Expose daemon on tcp://localhost:2375 without TLS" option works only for the first Docker run · Issue #3163 · docker/for-win · GitHub](https://user-images.githubusercontent.com/39293/50560459-a5db7300-0d09-11e9-8b81-0112134cd296.png)
Expose daemon on tcp://localhost:2375 without TLS" option works only for the first Docker run · Issue #3163 · docker/for-win · GitHub
![Connection refused message when i am trying to connect container - Compose - Docker Community Forums Connection refused message when i am trying to connect container - Compose - Docker Community Forums](https://global.discourse-cdn.com/docker/original/3X/0/f/0f37325e42c0c98029d4f93a6ae4fcbe68fb093d.png)
Connection refused message when i am trying to connect container - Compose - Docker Community Forums
![settings - Can i expose the daemon of 'docker for windows' on tcp://localhost:2375 using any command? - Stack Overflow settings - Can i expose the daemon of 'docker for windows' on tcp://localhost:2375 using any command? - Stack Overflow](https://i.stack.imgur.com/Ao5ZA.jpg)