Skip to content

examples: add archlinux.yaml #88

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

Merged
merged 2 commits into from
Jun 28, 2021
Merged

examples: add archlinux.yaml #88

merged 2 commits into from
Jun 28, 2021

Conversation

AkihiroSuda
Copy link
Member

No description provided.

Signed-off-by: Akihiro Suda <[email protected]>
@@ -0,0 +1,15 @@
arch: "x86_64"
images:
- location: "https://linuximages.de/openstack/arch/arch-openstack-LATEST-image-bootstrap.qcow2"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe add some comment here that this URL points to a symlink on the server. So Lima will cache this the first time it downloads the image, and will never refresh it unless the cache is manually pruned.

I noticed that e.g. the Debian sample points to snapshot from a specific day and not to a "latest" URL like https://cloud.debian.org/images/cloud/bullseye/daily/latest/debian-11-generic-amd64-daily.qcow2

So maybe Debian should be changed to, but I still wonder if there should be some mechanism to do some kind of cache validation? At least I think the user should see a message that they are using an outdated local cache version, and that a newer release is available for download.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I noticed that e.g. the Debian sample points to snapshot from a specific day

I wanted to do the same for archlinux, but https://linuximages.de/openstack/arch seems to retain old images only for a week 😞

So maybe Debian should be changed to, but I still wonder if there should be some mechanism to do some kind of cache validation? At least I think the user should see a message that they are using an outdated local cache version, and that a newer release is available for download.

I think we can use ETag.
(Side topic: we should also support validating SHA256)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(Side topic: we should also support validating SHA256)

Yes, I've been wondering if https://github.com/hashicorp/go-getter would be a good match for lima, but haven't really looked into it further. That is the library minikube is using for downloading files and validating their checksums.

@AkihiroSuda AkihiroSuda merged commit f187eb1 into master Jun 28, 2021
@AkihiroSuda AkihiroSuda deleted the dev-arch branch June 28, 2021 11:36
@AkihiroSuda AkihiroSuda added this to the v0.5.0 milestone Jun 29, 2021
@AkihiroSuda AkihiroSuda added the guest/archlinux Guest: Arch Linux label Jul 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
guest/archlinux Guest: Arch Linux
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants