A draft of the potential stream content. Understand your application, the framework it uses, and its recommend build practices Fully static apps ...that don't even require Node.js at runtime (e.g., a React SPA built with vite). A typical anti-pattern is (accidentally) leaving the Node.js runtime that was needed to build the app in the final prod image: FROM nginx:latest

Go to https://labs.iximiuz.com/challenges/kubernetes-pod-with-faulty-init-sequence or any other K8s-backed challenge, tutorial, or playground. Click "Start" and wait until it's warmed up. In the playground's web terminal, run kubectl proxy --address=0.0.0.0 --accept-hosts='.*' Expose the 8001 port using the "Expose HTTP port" button in the page header's right corner. Make sure to allow public access. On your local machine, create a kubeconfig file with the following content (using the URL generated on the previous step): # $(pwd)/kubeconfig apiVersion: v1 clusters: - name: cluster1

Slides. runc Article on iximiuz.com. We're going to need a Linux VM with two terminals. Basics: Non-interactive container First, prepare a new container: mkdir -p box1/rootfs cd box1

Prerequisites A Linux or macOS machine (2+ CPUs, 8+ GB RAM) running Docker git, cmake, curl [bonus] a local Kubernetes cluster (via kind or minikube) Intro Explain the idea real quick. Demo 1: Basics