Container Basics On Linux (Namespaces/Cgroups)

Peer into the abyss of your container namespaces

🧩 The Challenge

Trying to figure out why a process inside a container can’t talk to a socket on the host is a nightmare when you’re just guessing from the outside. I’ve spent way too many nights squinting at ps aux lists trying to map what’s actually running where.

💡 The Fix

Use nsenter to step right into the container’s shoes and run commands as if you were living inside that process’s environment. It saves you from installing debugging tools inside every single production image.

nsenter -t <pid> -n ip addr
nsenter -t <pid> -m -u -i -n -p ps aux

⚙️ Why It Works

By grabbing the PID of the target process, nsenter effectively switches your current shell into that container’s specific namespaces, letting you see the networking and process tree exactly how the container sees them. It bypasses the need for bloated container entrypoints just to run a quick trace.

🚀 Pro-Tip: Alias this as ‘enterpid’ in your bashrc and save your sanity.

Linux Tips & Tricks | © ngelinux.com | 11/15/2026