-
Notifications
You must be signed in to change notification settings - Fork 0
Image manager #3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Mesa DescriptionThis PR introduces the capability to export Docker images to a root filesystem (rootfs), enabling the creation of virtual machine filesystems directly from container images. The core of this change is a new This new functionality abstracts the image preparation process, allowing the system to leverage any OCI-compliant image from a container registry as a base for a virtual machine, rather than relying on pre-packaged rootfs tarballs. Description generated by Mesa. Update settings |
Mesa DescriptionThis change introduces the capability to export Docker/OCI container images to a root filesystem (rootfs). This allows the system to leverage the vast ecosystem of existing container images to create the base filesystem for new virtual machine instances. The new workflow integrates with the Docker daemon to pull a specified image and export its contents. This simplifies the process of creating and managing VM templates by replacing manual configuration with standardized, pre-built container images. Description generated by Mesa. Update settings |
rgarcia
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
very cool stuff!
cmd/api/api (handlers)
↓ depends on
lib/images, lib/instances, lib/volumes (domain)
↓ independent of
lib/oapi (API types)
See the README in lib/images/README.md for a summary