Selfhosted

40728 readers

595 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

213

PSA: Docker nukes your firewall rules and replaces them with its own. (sh.itjust.works)

submitted 9 months ago* (last edited 9 months ago) by [email protected] to c/selfhosted

50 comments fedilink hide all child comments

I use nftables to set my firewall rules. I typically manually configure the rules myself. Recently, I just happened to dump the ruleset, and, much to my surprise, my config was gone, and it was replaced with an enourmous amount of extremely cryptic firewall rules. After a quick examination of the rules, I found that it was Docker that had modified them. And after some brief research, I found a number of open issues, just like this one, of people complaining about this behaviour. I think it's an enourmous security risk to have Docker silently do this by default.

I have heard that Podman doesn't suffer from this issue, as it is daemonless. If that is true, I will certainly be switching from Docker to Podman.

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

[–] [email protected] -4 points 9 months ago (3 children)

What difference does it make if you open the ports yourself for the services you expose, or Docker does it for you? That's all that Docker is meant to do, act as convenience so you don't have to add/remove rules as the containers go up/down, or remember Docker interfaces.

If by any chance you are making services listen on 0.0.0.0 and covering them up with a firewall that's very bad practice.

[–] [email protected] 1 points 9 months ago (2 children)

There's no alternative for 0.0.0.0 and a firewall if you're e.g. using kubernetes.

[–] [email protected] -4 points 9 months ago (1 children)

I'm fairly sure you can find an alternative to whatever problem you're having.

[–] [email protected] 5 points 9 months ago

You need to be able to have multiple nodes in one LAN access ports on each others' containers without exposing those to the world and without using additional firewalls in front of the nodes.

That's why kubernetes ended up removing docker support and instead recommends podman or using containerd natively.