-
Notifications
You must be signed in to change notification settings - Fork 600
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
v1.0 roadmap: alpine: switch away from ISO to qcow2 #2366
Comments
I don't know what you mean by "ditched away", but I thought we had agreement that we would continue to support booting Lima instances from ISO/ramdisk1. So we would simply rename templates:
Are you planning anything else? Footnotes
|
I was thinking that we may remove, or at least deprecate, the ISO variant for sake of simplification |
We already did: #2236. I somewhat strongly oppose the removal of the ISO support. And several of the "stability" issues in the past have been caused by improper "fixes" for the benefit of colima, so that should no longer be an issue now that colima no longer uses Alpine. |
I think that the ISO/"LiveCD" support is a feature, and something that was also used by Docker Machine... It even had Debian support, even if that was never promoted. https://github.com/tianon/boot2docker-debian |
Is deprecation fine? |
I think switching the default would be enough, unless you want to drop alpine-lima from "upstream" (lima org)? Originally my suggestion was to provide multiple "editions", but I also don't know who would maintain them... But don't think it's deprecated? Possibly downstream-only (RD) Bundling the apk packages: Distro and engine examples: experimental/alpine-nerdctl: Alpine Linux, with containerd/nerdctl |
In Lima v1.0, the current ISO-based
alpine
template should be ditched away, and thealpine-image
(qcow2) template should take over the name ofalpine
The text was updated successfully, but these errors were encountered: