xref'ing bcvk
#4775
Replies: 1 comment
-
|
The lima user can use the new "_images" templates, if they don't want to think about qcow2 files... base:
- template:_images/ubuntuFor Lima we convert the container images to tarballs, since those simple files are easier to handle. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
There's so many projects which relate to "OCI containers and VMs"; lima is one, so is Kata Containers and apple/container etc. In the bootc side we have https://github.com/bootc-dev/bcvk which is as well.
It's a fundamentally different technology base than lima -
bcvk ephemerallaunches a container image with its rootfs mounted via virtiofs. The user never thinks about disk images (in contrast to lima which has qcow2 references in YAML).One obvious thing we could do here is
bcvk lima push <container image>which would be a lot likebcvk libvirt run- we'd do a fullbootc installto turn the container into a disk image, and then from there it becomes like any other disk image managed by lima.Though a possible flip side here is, in an ideal world bcvk would support MacOS - and finding the container images there is the tricky part. Like one use case here is where the user does a container build (or fetch) into the containerd storage inside a Lima VM, and we want to turn that into a new disk image on the host.
Of course a different thing we could do is just cross-reference the docs for the different projects, they're very related right now but still orthogonal - a user interested in one might actually want the other, etc.
Beta Was this translation helpful? Give feedback.
All reactions