Day-28
Before diving deep into storage concepts in Kubernetes, I decided to revisit Docker storage — and it turned out to be a great refresher!
Key Learnings:
1️⃣ Discovered how Docker images are built in multiple read-only layers, forming the base of immutable infrastructure.
2️⃣ Understood how containers create a writable layer on top of image layers for runtime changes.
3️⃣ Learned that data inside a container is temporary — it’s deleted when the container stops — and how volumes help make data persistent.
4️⃣ Explored storage drivers (like overlay2) that manage how layers and container data are stored and merged.
5️⃣ Created and attached Docker volumes using:
docker volume create data_volume
docker run -v data_volume:/app -dp 3000:3000 day27
and confirmed data persistence even after container removal.
6️⃣ Differentiated between volumes and bind mounts, understanding when to use each.
🔹 Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware ⸻ 1️⃣ Memory Ballooning (vmmemctl) Ballooning is the first memory reclamation technique used when ESXi detects memory pressure. ➤ Step-by-Step: How Ballooning Works 1. VMware Tools installs the balloon driver (vmmemctl) inside the guest OS. 2. ESXi detects low free memory on the host. 3. ESXi inflates the balloon in selected VMs. 4. Balloon driver occupies guest memory, making the OS think RAM is full. 5. Guest OS frees idle / unused pages (because it believes memory is needed). 6. ESXi reclaims those freed pages and makes them available to other VMs. Why Ballooning Happens? • Host free memory is very low. • ESXi wants the VM to release unused pages before resorting to swapping. Example • Host memory: 64 GB • VMs used: 62 GB • Free: 2 GB → ESXi triggers ballooning • VM1 (8 GB RAM): Balloon inflates to 2 GB → OS frees 2 GB → ESXi re...
Comments
Post a Comment