Confidential Containers with the Crun-Krun Container Runtime
summary
crun-krun wraps each container in a microv VM via the C library libkrun, using podman-built images (builda adds a CW/mkcw mode) and an external attestation server that alone holds the LUKS passphrase so attestation is required to unlock the root disk. claim: near‑zero CPU overhead for VM isolation; tradeoff: one VM per container makes namespace/resource sharing harder than Kata. demo: attestation returns the passphrase and the host cannot read the secret from the encrypted guest memory.
AI-written summary · about
chapters (12)
- 0:00Confidential containers intro
- 1:46What is confidential computing
- 3:12Need for VM attestation
- 4:58Building images for confidential computing
- 8:36Running workloads with Krun
- 12:31Krun attestation and decryption
- 16:04Live demo confidential execution
- 21:07Krun vs Kata Containers
- 22:33Resource sharing trade-offs
- 23:38Performance impact of confidential computing
- 24:44Memory encryption in trusted execution
- 25:06Q&A
related talks
33mDon't Peek Into my Container!
39mMore Than Secure: Containerd + KataContainers as Kubernetes Runtime
36mKata Containers: Hypervisor-Based Container Runtime
34mContainer Runtimes... on Lockdown: The Hidden Costs of Multi-tenant Workloads
14mA kernel? In a Container? Explain Yourself!
47mContainer Security
27mTrust No One: Bringing Confidential Computing to Containers
50mConfidential Containers: Why, How, and Where Are We?