liveBook · Manning

CAP_SYS_ADMIN

As explained in Podman in Action: Secure, rootless containers for Kubernetes, microservices, and more

CAP_SYS_ADMIN is a Linux capability that includes permission to perform filesystem mounts and many other system-administration operations.

CAP_SYS_ADMIN is a broad Linux capability that permits filesystem mounts and unmounts, among many other system-administration operations. Podman drops it from containers by default, so even root processes cannot remount read-only mount points. section 10.2.2 section 10.7

Rootful Podman running inside a container needs CAP_SYS_ADMIN to mount filesystems; --privileged supplies it. Rootless Podman instead uses CAP_SETUID and CAP_SETGID, which can support a narrower configuration. section 8.4.1 section 8.4.2

Run nested rootful Podman

podman run --privileged quay.io/podman/stable podman version demonstrates a nested Podman invocation that requires filesystem-mount permission. section 8.4.1

How Podman in Action: Secure, rootless containers for Kubernetes, microservices, and more covers it

How deep it goes
Explains broad administrative scope, mount control, container defaults, and isolation effects without enumerating every operation.
Examples
Uses privileged and capability-minimized Podman commands plus Kubernetes security contexts for rootful and rootless execution.
What it assumes
Assumes Linux container, capability, namespace, and Podman terminology while teaching why filesystem mounts require this capability.
What you can do after
Operate/configure nested Podman by granting CAP_SYS_ADMIN when required and preferring narrower rootless capability sets.
How it connects
Connects Linux capabilities with mount namespaces, rootless containers, user namespaces, Kubernetes, SELinux, and seccomp.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Podman in Action: Secure, rootless containers for Kubernetes, microservices, and more. The section links point to the parts of the book it draws on.