-
Notifications
You must be signed in to change notification settings - Fork 228
load container image from file #873
Comments
the only workaround i see, is serving the image from a local registry, and calling
|
Hi, at the moment, ignite uses the container runtime's content store to import images. The default container runtime being containerd, when ignite pulls an image, the image is pulled into the containerd image store and then copied to When you use a local registry, it still pulls the image into the container runtime content store. If the image is already in the content store, it can be directly imported into ignite with Hope that's helpful. |
Looks like I did work on this feature a long time ago but didn't finish it, maybe because the image store may change to use the containerd content store directly #557. |
Is there a way to run the VM from a squashfs or ext4 rootfs image directly as Firecracker suggests? My goal is to run container images directly beside a firecracker VM that runs a custom OpenWRT with a custom kernel that enables MPTCP. Seems like placing that custom kernel inside a docker image is not difficult. |
in docker we have
docker load
how does this work with ignite?
The text was updated successfully, but these errors were encountered: