OS updates
Updated
Virtainer Lite ships as one immutable host image. Updating is not a package upgrade: you point the host at a different image and reboot into it.
That is what makes the update reversible. The previous image stays on disk, so going back is a reboot rather than a restore.
Switching image
Section titled “Switching image”-
Open OS Updates. The page shows the image reference the host is running now and its version.
-
Enter the target image reference. It is free text, so you can move to a newer release, or deliberately back to an older one.
-
Choose how to apply it.
- Switch and reboot stages the new image and reboots into it.
- Stage only prepares it and leaves the host running as it is. Reboot later, on your own schedule, to activate it.
Rolling back
Section titled “Rolling back”If a new image misbehaves, reboot into the previous one. The host keeps the image it was running before the switch, so recovery is a single reboot and does not depend on a backup.
Machines across an update
Section titled “Machines across an update”A host reboot stops every machine. When the host comes back, machines that were running are started again, and their addresses are preserved. See After a host reboot for the details and the failure cases.
Nothing about your machines lives in the host image. Configuration and data persist across the switch; only the host system is replaced.
Externally managed hosts
Section titled “Externally managed hosts”If the host was not installed from a Virtainer image, the page says so and the switch is unavailable. Update it the way you update the rest of that system.
Registries
Section titled “Registries”The image reference you enter must be reachable over a valid TLS connection. There is no option to disable certificate checking. A registry using plain HTTP or a self-signed certificate has to be trusted by the host image itself.