mirror of
https://github.com/containers/podman.git
synced 2025-06-02 02:26:52 +08:00
9abe8c7853
Podman machine os apply takes a takes a OCI image with container native ostree functionality and rebases the machine os on that image. Currently, this requires the guest os inside the vm to use rpm-ostree. When specifying an image, any container transport may be specified. If a container transport is not specified, OS apply will attempt to search the local containers-storage for the image, and if it is not found, it will then attempt to use the Docker transport to pull from a remote registry. The architecture of OS apply is as follows: podman machine os apply ssh's into the machine and calls podman machine os apply. on the secondary call to podman machine os apply, apply recognizes that it is inside the machine and does image operations, and finally calls rpm-ostree rebase. Tests are written but commented out, due to the chicken-and-egg problem. Signed-off-by: Ashley Cui <acui@redhat.com>
1.1 KiB
1.1 KiB
% podman-machine-os-apply 1
NAME
podman-machine-os-apply - Apply an OCI image to a Podman Machine's OS
SYNOPSIS
podman machine os apply [options] image [vm]
DESCRIPTION
Apply machine OS changes from an OCI image.
VM's that use OS's that use rpm-ostreee have the capability to rebase itself from the content of an OCI image.
podman machine image apply takes an OCI image with container native ostree functionality and rebases itself on that image.
By default, Podman machines on Mac and Linux use an rpm-ostree based distrubition (Fedora CoreOS).
For more information, please see the rpm-ostree docs.
OPTIONS
--help
Print usage statement.
--restart
Restart VM after applying changes.
EXAMPLES
$ podman machine os apply quay.io/podman_next
$ podman machine os apply quay.io/podman_next podman-machine-defualt
SEE ALSO
podman(1), podman-machine(1), podman-machine-os(1)
HISTORY
February 2023, Originally compiled by Ashley Cui acui@redhat.com