Skip to content

What is Virtainer Free?

Updated

Virtainer Free is self-hosted virtualization that runs on one host. You give it a Linux cloud image or an OCI (Docker) image, and it runs that image as a full virtual machine on your own hardware, with its own kernel, its own storage, and a hardware-enforced isolation boundary.

Install one appliance on your host and operate it from the web UI or API. There is no separate orchestration stack to assemble. Virtainer Free is generally available now.

The entire product lives on that one host, with no separate control plane to install:

  • the web UI and the API
  • the VM and AppVM engine
  • an image cache
  • storage and network setup
  • metrics
  • the full machine lifecycle

Virtainer Free runs two kinds of machine from the same engine:

Type Source image What you get
VM A standard Linux cloud image A normal Linux server, with cloud-init, disks, networking, and a console.
AppVM Any Docker / OCI image The application image booted as its own VM, with its own kernel and disk and no container engine inside the guest.

A VM behaves like any cloud instance you have run before. Pick a Linux cloud image, let cloud-init handle first-boot configuration, attach disks and networking, and open a Shell or the serial Rescue console.

An AppVM runs a Docker or OCI application image as its own virtual machine. Import the image, choose its resources and networking, then start it. Virtainer provides the environment needed to boot it, along with auto-restart, resource limits, sealed secrets and health checks. A running AppVM does not need access to its source registry.

AppVMs are a Preview feature, and the console marks their sidebar group Preview. You can run an AppVM stateless or keep its disk across reboots. It is built for code you do not fully control, such as AI agents, untrusted or third-party images, and internal services you want to keep apart, but ordinary services like nginx run exactly the same way.

Most workloads are placed by choosing between two models:

  • Virtual machines give strong isolation, with a separate kernel behind a hardware boundary. They are also heavy and slow to start.
  • Containers are fast and dense, but they share the host’s kernel, so the boundary between workloads is a kernel feature rather than hardware.

Virtainer combines hardware-isolated machines with the convenience of application images. You can run cloud images and application services from the same console without installing a container orchestration platform.

Virtainer Free ships as a single, self-contained appliance image. The host system is immutable: your configuration and data persist, and everything else is read-only. Updating the host is an image switch rather than a package upgrade. You can stage it ahead of time, and the image you were running stays on disk as the previous deployment, so sudo bootc rollback --apply on the host boots back into it. That rollback reaches only the one previous deployment. You always know which version a host is running, and there is no configuration drift to track down.

  • Resilient storage: pool multiple drives with redundancy, with early warning when a disk starts to fail.
  • Bridged networking: each machine gets a real presence on your network through a Linux Layer 2 bridge, with optional anti-spoofing and port isolation.
  • Resource control: cap CPU, memory, and disk I/O per machine so one machine cannot starve the others.

Virtainer Free is the single-host edition, and it runs everything described above on one machine. Virtainer Pro adds a central layer for running more than one host as a cluster. It is coming soon.

Start here and work down, or jump to the part you need: