-
Notifications
You must be signed in to change notification settings - Fork 660
Adds latest still supported ubuntu lts templates #2433
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
Adds latest still supported ubuntu lts templates #2433
Conversation
examples/ubuntu-22.04.yaml
Outdated
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.
Should we now mv ubuntu.yaml ubuntu-24.04.yaml; ln -s ubuntu-24.04.yaml ubuntu.yaml
for consistency?
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.
Would be ok
- location: "https://cloud-images.ubuntu.com/releases/20.04/release-20240612/ubuntu-20.04-server-cloudimg-amd64.img" | ||
arch: "x86_64" | ||
digest: "sha256:7fce49f6c9afd2cdd9c26618b056f8806e500dd4d6eff516c9c6b5fab12e7f79" | ||
- location: "https://cloud-images.ubuntu.com/releases/20.04/release-20240612/ubuntu-20.04-server-cloudimg-arm64.img" |
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.
It is hard to keep every image up-to-date, so we may need to have an automation script before adding new templates
Ubuntu 16.04 and 18.04 are probably old enough to hide them from the general public (even if supported) Having 20.04 and 22.04 should be old enough I think? And then we don't have to re-live all old bugs, like: Should probably delete centos-7.yaml (after tomorrow) as well, even if it is from 2014 rather than 2018... |
Sorry, but my intention with this PR is only to introduce common ubuntu templates, not change anything not having a relation with them. I agree automation to ensure latest releases would be great, but even in my case, an update after deployment is not such a pain, as usually even in public cloud environments, full upgrade is part of my cloud-init setup (even public cloud ain't having latest and greatest releases). For next step, I'm willing when I get some time off for some automation for some of the templates that concern me, being Debian and Ubuntu, as I don't use any other distributions for server work. |
We now have an updater for Ubuntu (https://github.com/lima-vm/lima/blob/master/hack/update-template-ubuntu.sh), so this PR can be revisited again after rebasing. |
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.
This should be probably removed due to EOL
Opened an alternative PR: |
I wanted to add a few more ubuntu lts templates that I use often on local work I do and thought it would be useful for others to have them available.