this post was submitted on 26 Oct 2023
81 points (94.5% liked)

Selfhosted

40329 readers
426 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

I keep reading about podman, yet it doesm't FEEL as mature to me as docker for a normal user like me. What's your opinion? Did you already switch or do you keep waiting for ... for what? When will you switch?

you are viewing a single comment's thread
view the rest of the comments
[–] lemmyvore@feddit.nl -1 points 1 year ago* (last edited 1 year ago)

When you install Apache on the host then yes, you just need a rule to allow the port. But a container runs on a separate network interface, which means you also (1) need to know the name of the interfaces involved, which change for each container and their network mode and the host's network adapter and so on, and (2) set up rules to forward the port traffic between the container interface and the host interface.

I'm guessing you haven't checked to see what Docker is actually doing, or you've looked only at the OUTPUT and INPUT chains.

I'm also guessing that when you stop Apache you leave the ports open in the firewall. Which is bad practice. Docker takes down the rules when the container stops, which ends up as better security.

I sincerely hope you're not actually running a machine that's just a firewall away from the Internet, because blaming Docker for bad security in that case is very shortsighted. Docker is actually helping you by making correct and complete firewall rules.

podman, a drop in replacement for docker, does implement this in another way

Yeah? How does it do that?