Container Basics On Linux (Namespaces/Cgroups)
Stop guessing what a container process can actually see
🧩 The Challenge
Dealing with a container that behaves like it’s in a different universe is exhausting, especially when you can’t tell if your file system mount is actually visible to the process inside. I’ve wasted hours tracing paths that shouldn’t have been there but were somehow linked in a private mount namespace.
đź’ˇ The Fix
You can jump into the namespace of a running process using nsenter to see exactly what that container sees, saving yourself the headache of blindly guessing at mount points.
nsenter -t <pid> -m -u -i -n -p /bin/bash⚙️ Why It Works
By attaching your shell to the target PID’s namespaces, you’re effectively stepping into its local reality where mounts, network interfaces, and process IDs reflect the container’s isolated view rather than the host’s.
🚀 Pro-Tip: Use readlink /proc/<pid>/ns/* to quickly check if two processes are even running in the same namespace buckets before you start debugging.
Linux Tips & Tricks | © ngelinux.com | 10/5/2026