Container Basics On Linux (Namespaces/Cgroups)

Stop unshare from leaving your processes stranded in the wrong namespace

🧩 The Challenge

Every time I try to test process isolation with unshare, I end up stuck in a weird shell where none of my network tools work and I have no idea how I got there. It is way too easy to lose track of what namespaces you are actually joined to when you are digging through the kernel internals.

💡 The Fix

You should use the readlink command on the proc filesystem to verify exactly which namespace IDs you are currently sitting in. It is a quick sanity check before you go changing things and lose your connection.

readlink /proc/$$/ns/net
readlink /proc/$$/ns/mnt

⚙️ Why It Works

The proc directory exposes these namespaces as symbolic links where the target indicates the specific ID of the namespace currently assigned to that process ID. If the links for two different processes point to the same ID, you know for a fact they are sharing that namespace context.

🚀 Pro-Tip: Keep a separate terminal open in the parent namespace to act as your escape hatch if you accidentally lock yourself out of your own network interface.

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