Selfhosted

40211 readers

1167 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 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

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

submitted 8 months ago* (last edited 8 months ago) by Kalcifer@sh.itjust.works to c/selfhosted@lemmy.world

45 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

[–] N0x0n@lemmy.ml 0 points 8 months ago (1 children)

Option to disable this behavior would be 100x better then current, but what do I know lol

Prevent docker from manipulating iptables

Don't know what it's actually doing, I'm just learning how to work with nftables, but I saved that link in case oneday I want to manage the iptables rules myself :)

[–] Auli@lemmy.ca 0 points 8 months ago (1 children)

Good luck. Your going to have to change the rules whenever the up address of the container changes.

[–] N0x0n@lemmy.ml 1 points 8 months ago* (last edited 8 months ago)

If you are talking about the IP address then just add a static address, no? I do it anyway in my docker compose:

...
    networks:
      traefik.net:
        ipv4_address: 10.10.10.99

networks:
    traefik.net:
      name: traefik-net
      external: true

I'm not an expert so maybe I'm wrong, if so do not hesitate to correct me !

EDIT: If the IP address doesn't change, you do not need to change to routing and iptables/nftables rules. ??