Rootless Containers and Tradeoffs
On this page
What Rootless Gives You
- Reduces privilege: container runtime runs without root on the host.
- Limits host compromise impact, but introduces constraints.
Common Constraints
- Low ports (<1024) require extra setup.
- Some storage/network features differ by distro/kernel.
- File ownership mappings can surprise you (user namespaces).
Quick Checks
id cat /proc/sys/user/max_user_namespaces 2>/dev/null || true cat /etc/subuid 2>/dev/null | head -5 || true cat /etc/subgid 2>/dev/null | head -5 || true
Troubleshooting Pattern
- Start with permissions and paths; then check user namespace mappings.
- Prefer explicit volume ownership to avoid runtime surprises.
Failure Modes
- Permission denied: volume ownership mismatch.
- Networking oddities: rootless networking backend limitations.