Tag: #firecracker

한국어English日本語中文

← All posts

• AWS Lambda MicroVMs — Running Agent-Written Code Under VM Isolation, and the New Problem Snapshots Create

  AWS launched Lambda MicroVMs on June 22, 2026. It sells Firecracker micro-VMs as a service, and the market it's aiming at is clear — running user- or AI-generated code, isolated per tenant. It moves the container's share

  2026-07-16 · 17 min read #security#firecracker#microvm#aws-lambda#sandboxing

• Container Runtimes 2026 Deep Dive - containerd, runc, Podman, CRI-O, Kata, gVisor, Firecracker, Wasm

  A full-stack tour of production container runtimes as of May 2026. We cover containerd (de facto Kubernetes CRI), low-level OCI runtimes runc, crun, and youki, the alternative CRI CRI-O, the rootless/daemonless trio Podm

  2026-05-16 · 16 min read #container-runtime#containerd#runc#podman#cri-o

• Container Runtime Alternatives 2026 Deep Dive - containerd, CRI-O, Podman, runc, gVisor, Kata Containers, youki, WasmEdge, and Firecracker

  The container runtime landscape in 2026 is no longer Docker-centric. Kubernetes removed dockershim in 1.24, and containerd 2.0 and CRI-O 1.31 have become the cluster default. On developer workstations Podman 5 and Docker

  2026-05-16 · 18 min read #english#container-runtime#containerd#cri-o#podman