Instead of running your applications in containers, Fly.io *used* to unpack your Docker images onto light-weight virtual machines called Fly Machines. But now, we DO use containers. In this video we talk about why and HOW.

NOTE: While all apps now run in containers on Fly Machines, as I mention in the video, **the ability to actually run multiple containers per Machine is limited** to Fly Kubernetes users OR people directly working with the Machines API. This is likely to change in the future though!

Official announcement on Fresh Produce:
https://community.fly.io/t/docker-without-docker-now-with-containers/22903

Fly.io offers insights into edge computing, serverless architecture, and global content delivery network (CDN), providing documentation, tutorials, and best practices for deploying and scaling applications at the network edge. By exploring Fly.io's curated content, developers can learn about Fly's edge computing platform, distributed application runtime, and HTTP/2 load balancing for building fast, secure, and scalable web applications. Whether you're optimizing latency for global users, offloading compute-intensive tasks, or deploying microservices, Fly.io offers resources to supercharge your application performance and reliability.

Fly.io

Fly.io now supports running containers inside fly machines, a shift from their previous method of unpacking Docker images directly onto lightweight virtual machines. This change, driven by the need for sidecar containers in their managed Kubernetes service, improves flexibility and allows for tighter coupling of services. Fly machines use a combination of Firecracker hypervisor and the pilot init process to manage containers, making it possible to deploy and manage multiple images separately within a single virtual machine.

We use containers now. Here's why.