Loading video player...
In this episode, we break down Docker containers and kubernetes (k8s) in practical terms (what they are, why they’re small, and what “done correctly” looks like, including in cloud computing), then tackle the classic DevOps problem: “it works on my machine” — and how container images help eliminate environment drift. We finish with a sharp question that matters in real production stacks: is Kubernetes actually the orchestrator, or is it being orchestrated by other tools? If you’re working with Docker, container images, Kubernetes, CI/CD, platform engineering, or cloud-native infrastructure, this one will help you think more clearly about what’s really happening across dev, build, and deploy. Key topics ► What a container actually is (and what it isn’t) ► Why containers reduce “works on my machine” failures ► Container images, reproducibility, and deployment consistency ► The Kubernetes “orchestrator” debate in modern toolchains Chapters 00:00:00 Intro + what we’re covering (containers, Docker, Kubernetes) 00:02:15 What a container is (practical definition) 00:06:45 VMs vs bare metal: networking, IPs, resilience 00:09:06 Why containers are small (MB) vs VMs (GB) — speed + portability 00:12:00 “Works on my machine” — images, immutability, repeatability 00:15:00 Dockerfile → Docker build → image (what the artefacts are) 00:18:00 Running the same image anywhere (dev → server → platform team) 00:22:30 Kubernetes basics: YAML manifests + desired state (replicas etc.) 00:27:00 Why Kubernetes feels hard (cluster components + complexity) 00:30:45 Managed Kubernetes: what it abstracts (and what it doesn’t) 00:32:46 Is Kubernetes really the orchestrator? + when not to use K8s 00:35:15 Alternatives / simpler approaches (e.g., “just run Docker on a server”) 00:38:15 Wrap-up: when to use VMs vs containers + orchestration summary #DevOps #Docker #Kubernetes #Containers #CICD #PlatformEngineering #CloudNative