UTS Namespace Explained: How Containers Get Their Own Hostname (Linux → Docker → Kubernetes)

In this episode, we break down one of the most fundamental Linux isolation building blocks — the UTS Namespace.
You’ll understand how containers get their own hostname, how Kubernetes pods share identity, and why this namespace is the simplest yet most powerful part of container internals.
---

0:00 What are Linux Namespaces
6:14 What is a UTS Namespace
6:56 Demo of hostname command on host OS
7:54 Demo using `unshare` command to create a UTS namespace
10:41 Demo on how docker makes use of the UTS namespace
15:39 Demo on how Kubernetes makes use of UTS namespace
19:25 Summary of UTS namespace

---

🔍 What you’ll learn:

What is the UTS namespace in Linux?

How unshare creates an isolated environment

Why changing hostname inside a namespace doesn’t affect the host

How Docker uses UTS to give containers unique names

How Kubernetes Pods share UTS namespaces

Visual demo + full command walkthrough

Real-world mapping: Linux → Container Runtime → Kubernetes

🧪 Commands used in the demo:

hostname

sudo unshare --fork --uts bash

sudo hostname demo-container

Docker hostname check: docker run -it alpine sh

Kubernetes: kubectl exec -it pod -- hostname

📌 Why this matters

Understanding namespaces helps you truly understand how Docker and Kubernetes isolate workloads.
This is Part 1 of the Namespaces Series (1/4).
🔔 Coming next

Episode 2: PID Namespaces — How Containers Get Their Own Process ID

#LinuxForDevOps
#KubernetesTutorial
#DockerInternals
#K8sForBeginners
#CloudNative
#SRE
#DevOpsTraining
#LearnDevOps
#LinuxKernel
#ContainerInternals
#K8sPod
#DockerLearning
#TechEducation
#InfrastructureEngineering

Видео UTS Namespace Explained: How Containers Get Their Own Hostname (Linux → Docker → Kubernetes) канала BashLab