It could be seen as a *security issue*, in my opinion.
If a server or a user is expecting to block thing behind ufw install.
And then he/she install docker with its default, it will bypass the existing firewall configuration. So exposing thing that was blocked previously.
It could be seen as a *security issue*, in my opinion.
If a server or a user is expecting to block thing behind ufw install.
And then he/she install docker with its default, it will bypass the existing firewall configuration. So exposing thing that was blocked previously.
Without any notification.
Available ref:
- https:/ /docs.docker. com/engine/ network/ packet- filtering- firewalls/ #docker- and-ufw - warning on docker side /github. com/chaifeng/ ufw-docker - some script and fixes on ufw side /stackoverflow. com/questions/ 30383845/ what-is- the-best- practice- of-docker- ufw-under- ubuntu /github. com/moby/ moby/discussion s/45524 - discussion on docker side
- https:/
- https:/
- https:/
obviously things get very complicated here... 😉