Files
podman/pkg/machine/define/config.go
Brent Baude 2430fc71a0 Allow podman machine to download from oci registry
this pr represents a shift in how we download podman machine images.
these images will now be stored in oci registry and will replace the
default method of downloading an image.  you can still use a reference
to a disk image as a path or url too with the --image-path switch.

the final registry and location of the images has not been determined;
and will need to be updated in podman as well.

i dont think we need to allow --image-path to accept a registry/image
for the podman 5.0 release.  i do think there will be demand for this.

upgrades also need to be plumbed.  for example, updating from an oci
registry.

once we make decisions on final image locations/registrties as well as
some behaviors of init and the oci pull, we must update the machine-init
documentation.

Signed-off-by: Brent Baude <bbaude@redhat.com>
2024-02-12 15:19:34 -06:00

25 lines
427 B
Go

package define
import "os"
const UserCertsTargetPath = "/etc/containers/certs.d"
const DefaultIdentityName = "machine"
var (
DefaultFilePerm os.FileMode = 0644
)
type CreateVMOpts struct {
Name string
Dirs *MachineDirs
ReExec bool
UserModeNetworking bool
}
type MachineDirs struct {
ConfigDir *VMFile
DataDir *VMFile
ImageCacheDir *VMFile
RuntimeDir *VMFile
}