Support host network mode about ufw-docker-automated HOT 5 CLOSED

It appears that with --net=host we just need to do some regular ufw allow from commands instead of ufw route allow from. What remains to assert is how to retrieve ports used by the container and how to delete those ufw rules when the container is deleted.

Maybe using container.attrs['Config']['ExposedPorts'] when EXPOSE is specified in the dockerfile.

from ufw-docker-automated.

I worked on that on net-host branch, I think for now in host network mode we can only handle incoming traffic (ufw-from label).
For outgoing traffic (ufw-to label), it's a bit more tricky. Maybe we need to do something like this :

ufw allow out to any port 53
ufw allow out to 192.168.1.0/24 port 80 proto tcp
ufw deny out to any

from ufw-docker-automated.

Maybe we shouldn't do host network mode, because there is no IPtables involved and users can simply create normal ufw rules. What do you think? 🤔

from ufw-docker-automated.

I agree, this could get confusing because we are touching rules that the user maybe want to manage.
It's doable but it requires that the user understands what it does.
I'll leave the idea in the branch net-host, but as you can see the hack is not pretty when I need to remove rules (line 125).

from ufw-docker-automated.

Indeed, Let's say doable, but not required. As it would make things over complex.

from ufw-docker-automated.