ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
DevOps & observability · #podman
Learn how to configure rootless Podman using User Namespaces to eliminate root-privileged daemons and enhance host security through subuid and subgid mapping.
Stop relying on root-privileged daemons. Learn how Podman uses User Namespaces and slirp4netns to run secure, rootless containers that limit the blast radius of potential escapes.
Learn how Podman uses User Namespaces and subordinate UIDs to run containers without root privileges, reducing the host attack surface while maintaining container functionality.
Stop relying on root-privileged daemons. Learn how Podman's rootless mode uses user namespaces and slirp4netns to isolate containers and reduce the host attack surface.
Rootless Podman maps container 'root' to an unprivileged host UID via user namespaces and subuid ranges — shrinking the blast radius of escapes and removing the privileged daemon. Here's how it works, how to verify it, and where the trade-offs bite.
Learn when to use Podman rootless versus rootful execution, see a comparison table, and validate your setup with a single command.
Is it possible to... run a container with podman which has an IP on the same subnet that the host is on is accessible from every other host on the subnet including the host itself ? I had partial success using both a macvlan and ipvlan drivers - I am able to run a container, give it an IP address, and this IP is then accessible from every other host on the n
Automating Rootless Container Lifecycles Creating a repeatable development environment often requires containers to start automatically upon system boot, regardless of whether the developer has an active SSH or local session. Podman facilitates this by allowing the generation of systemd unit files to manage containers as user-level services. Session Boundary
I have two nginx containers running. One is listening on port 80 the other 8080. Here is how I run them: sudo podman run --rm \ -t \ -p 8080:80 \ --publish-all \ --name nginx-two \ -v ./html2/:/usr/share/nginx/html \ -v ./html2/conf/default.conf:/etc/nginx/conf.d/default.conf \ -d nginx The second: sudo podman run --rm -t -p 80:80 --name nginx -v ./html/:/us
docker
nginx