Container Basics On Linux (Namespaces/Cgroups)

Stop worrying if your container really sees the host network

🧩 The Challenge

You’ve probably spent hours debugging why your container can’t talk to a local service, only to realize you accidentally stuck it in a completely different network namespace. It’s a classic headache that makes you feel like you’re losing your mind when local ports just vanish.

💡 The Fix

Use nsenter to dive into the specific namespace of your container and check the routing table exactly how the container sees it. It saves you from having to guess what’s going on behind the abstraction layer.

nsenter -t $(docker inspect -f '{{.State.Pid}}' <container_name>) -n ip addr

⚙️ Why It Works

By grabbing the PID of the container’s process, this command forces your shell into the container’s network namespace instead of the host’s, letting you see the interface configuration firsthand.

🚀 Pro-Tip: Alias this to something short like ‘nenter’ if you’re doing a lot of deep-dive debugging on production clusters.

Linux Tips & Tricks | © ngelinux.com | 10/28/2026