Programmer Humor

33371 readers

1214 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

Keep content in english
No advertisements
Posts must be related to programming or programmer topics
- If the mod doesn't find it funny, you're banned. Ha-ha!... For real: do not use the community for "statements". There are other places for such content. Keep it chill and funny.

founded 3 years ago

MODERATORS

Feyter@programming.dev

anzo@programming.dev

BurningTurtle@programming.dev

pylapp@programming.dev

525

Context: Docker bypasses all UFW firewall rules (lemmy.world)

submitted 1 year ago* (last edited 1 year ago) by qaz@lemmy.world to c/programmer_humor@programming.dev

99 comments fedilink hide all child comments

Docker docs:

Docker routes container traffic in the nat table, which means that packets are diverted before it reaches the INPUT and OUTPUT chains that ufw uses. Packets are routed before the firewall rules can be applied, effectively ignoring your firewall configuration.

you are viewing a single comment's thread
view the rest of the comments

[–] exu@feditown.com 15 points 1 year ago (1 children)

network: host gives the container basically full access to any port it wants. But even with other network modes you need to be careful, as any -p <external port>:<container port> creates the appropriate firewall rule automatically.

[–] AmbiguousProps@lemmy.today 3 points 1 year ago

I just use caddy and don't use any port rules on my containers. But maybe that's also problematic.