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.
Quick Guide to VCF Automation for VCD Administrators VMware Cloud Foundation 9 (VCF 9) has been released and with it comes brand new Cloud Management Platform – VCF Automation (VCFA) which supercedes both Aria Automation and VMware Cloud Director (VCD). This blog post is intended for those people that know VCD quite well and want to understand how is VCFA similar or different to help them quickly orient in the new direction. It should be emphasized that VCFA is a new solution and not just rebranding of an old one. However it reuses a lot of components from its predecessors. The provider part of VCFA called Tenenat Manager is based on VCD code and the UI and APIs will be familiar to VCD admins, while the tenant part inherist a lot from Aria Automation and especially for VCD end-users will look brand new. Deployment and Architecture VCFA is generaly deployed from VCF Operations Fleet Management (former Aria Suite LCM embeded in VCF Ops. Fleet Management...
Comments
Post a Comment