4 ms·
i'm very embarrassed to admit this, but i literally just discovered this. thought ufw was literally last defense. gotta run to fix this (luckily, all just pet
by giansegato 5y ago
i'm very embarrassed to admit this, but i literally just discovered this. thought ufw was literally last defense. gotta run to fix this
(luckily, all just pet projects with no sensitive stuff - still…)
- jeroenhd 5y agoHa, this reminds me of the day I found out. I've port scanned my own servers ever since, just in case. It's such an easy footgun to fall for, they should really put a big scary warning somewhere on the Docker installation page for Ubuntu or something.
- diftraku 5y agoWe had this issue previously and solved it with ufw by using the built-in DOCKER-USER chain that allows you to filter traffic before it hits Docker's own rules. Adding the relevant lines to UFW's before.rules means they persist across reloads. For more on Docker's built-in chains, see: https://docs.docker.com/network/iptables/#add-iptables-policies-before-dockers-rules https://docs.docker.com/network/iptables/#add-iptables-polic...