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
[–] 108 points 1 year ago (16 children)

This was a large part of the reason I switched to rootless podman for everything

  • source
  • hideshow 16 child comments
  • [–] 21 points 1 year ago (6 children)

    Explicitly binding certain ports to the container has a similar effect, no?

  • source
  • parent
  • hideshow 6 child comments
  • [–] 10 points 1 year ago (4 children)

    I still need to allow the ports in my firewall when using podman, even when I bind to 0.0.0.0.

  • source
  • parent
  • hideshow 4 child comments
  • [–] [S] 3 points 1 year ago (3 children)

    Also when using a rootfull Podman socket?

  • source
  • parent
  • hideshow 3 child comments
  • [–] 10 points 1 year ago (7 children)

    My problem with podman is the incompatibility with portainer :(

    Any recommendations?

  • source
  • parent
  • hideshow 7 child comments
  • [–] 15 points 1 year ago (2 children)

    cockpit has a podman/container extension you might like.

  • source
  • parent
  • hideshow 2 child comments
  • [–] [S] 8 points 1 year ago* (last edited 1 year ago) (1 child)

    It's okay for simple things, but too simple for anything beyond that, IMO. One important issue is that unlike with Portainer you can't edit the container in any way without deleting it and configuring it again, which is quite annoying if you just want to change 1 environment variable (GH Issue). Perhaps they will add a quadlet config tool to cockpit sometime in the future.

  • source
  • parent
  • hideshow 1 child comment