-
Notifications
You must be signed in to change notification settings - Fork 624
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
Added OpenSUSE aarch64 #1450
Added OpenSUSE aarch64 #1450
Conversation
Strange this image isn't mentioned on the regular download page https://get.opensuse.org/leap/15.4/#download Seems correct, boots OK |
TBH I saw the link here https://en.opensuse.org/openSUSE:AArch64#Running_openSUSE_from_raw_image
🎉 |
@jandubois LGTY? |
examples/opensuse.yaml
Outdated
digest: "sha256:378c51ae8a064513410285ffe884fa455e6325c583861aebe11cff7291298195" | ||
- location: https://download.opensuse.org/distribution/leap/15.4/appliances/openSUSE-Leap-15.4-ARM-JeOS-efi.aarch64.qcow2 | ||
arch: "aarch64" | ||
digest: "sha256:79d63c9096e13fc5b615c4807ac845b3afe6bed4f4d71ae257f764d4ac2e11fc" |
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.
The digest changes day by day, so it shouldn't be pinned
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.
@e-minguez Please drop this digest, and I'm happy to merge this PR.
Migration to Minimal-VM can be discussed later.
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.
I don't see the digest changing; it just looks like the digest in the PR is wrong. The correct digest should be:
$ cat openSUSE-Leap-15.4-ARM-JeOS-efi.aarch64.qcow2.sha256
965691484a2033f95789050820921ab847d1827a375038831aa7a237718099a5 openSUSE-Leap-15.4-ARM-JeOS-efi.aarch64.qcow2
Hi, If you wish to use ARM images built by the Minimal-VM team (formerly known as the JeOS team) from SUSE, please use the following:
As a reminder the Minimal-VM team at SUSE built identical images for SLES and openSUSE Leap/TW, but the openSUSE ARM community build their own images with their own packages lists/requirements. The openSUSE ARM Community didn't want to drop the JeOS name to avoid confusion with the openSUSE/SLES JeOS images built by SUSE, thus the SUSE team decided to rename JeOS to Minimal-VM starting with 15.4. So if you see any images for 15.4 and 15.5 that still has "JeOS" in the name, this means that you are using an images built by the openSUSE ARM Community but not the ones built by the Minimal-VM team from SUSE. I hope this clarify and helps you decide which images to use. Regards, |
It's unfortunately hidden behind the "Alternative downloads" link. |
Actually that was the one I was trying to link, but it was confused: Download: https://get.opensuse.org/leap/15.4/#download Alternative downloads: https://get.opensuse.org/leap/15.4/# (no "Cloud image" for arm(64)) It is missing from both of them, referring to yet another third page. https://en.opensuse.org/Portal:Arm#Release_supported_platforms I guess it is the Just Enough Operating System confusion from above ? |
Basically, yes. IMO having a wiki page for the huge list of "community" JeOS images makes sense, but it's confusing that the Minimal-VM images are listed on the download page explicitly. Ideally it should also be explained what the differences are... |
|
Please squash commits, and update the PR title |
examples/opensuse.yaml
Outdated
@@ -3,7 +3,9 @@ images: | |||
# Hint: run `limactl prune` to invalidate the "Current" cache | |||
- location: https://download.opensuse.org/distribution/leap/15.4/appliances/openSUSE-Leap-15.4-JeOS.x86_64-15.4-OpenStack-Cloud-Current.qcow2 | |||
arch: "x86_64" | |||
# No aarch64 OpenStack build found :( | |||
digest: "sha256:378c51ae8a064513410285ffe884fa455e6325c583861aebe11cff7291298195" |
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 digest has to be removed too
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.
Why, it seems to be correct:
$ cat openSUSE-Leap-15.4-JeOS.x86_64-OpenStack-Cloud.qcow2.sha256
378c51ae8a064513410285ffe884fa455e6325c583861aebe11cff7291298195 openSUSE-Leap-15.4-JeOS.x86_64-OpenStack-Cloud.qcow2
And I've successfully created an openSUSE instance with it:
$ l start examples/opensuse.yaml
? Creating an instance "opensuse" Proceed with the current configuration
INFO[0000] Attempting to download the image arch=x86_64 digest="sha256:378c51ae8a064513410285ffe884fa455e6325c583861aebe11cff7291298195" location="https://download.opensuse.org/distribution/leap/15.4/appliances/openSUSE-Leap-15.4-JeOS.x86_64-15.4-OpenStack-Cloud-Current.qcow2"
INFO[0001] Using cache "/Users/jan/Library/Caches/lima/download/by-url-sha256/27f3bb70bbc178edcae8edd360883ca9f2c9dc88c9d83cecd7d5b9752347ad05/data"
[...]
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.
The JeOS checksum seems unchanged across some mirrors:
$ FILE=distribution/leap/15.4/appliances/openSUSE-Leap-15.4-JeOS.x86_64-OpenStack-Cloud.qcow2.sha256
$ curl https://download.opensuse.org/$FILE
378c51ae8a064513410285ffe884fa455e6325c583861aebe11cff7291298195 openSUSE-Leap-15.4-JeOS.x86_64-OpenStack-Cloud.qcow2
$ curl https://mirror.csclub.uwaterloo.ca/opensuse/$FILE
378c51ae8a064513410285ffe884fa455e6325c583861aebe11cff7291298195 openSUSE-Leap-15.4-JeOS.x86_64-OpenStack-Cloud.qcow2
$ curl https:///mirror.its.dal.ca/opensuse/$FILE
378c51ae8a064513410285ffe884fa455e6325c583861aebe11cff7291298195 openSUSE-Leap-15.4-JeOS.x86_64-OpenStack-Cloud.qcow2
However, there is something wrong with the checksums on openSUSE mirrors; I've noticed this for the Minimal image now:
$ FILE=distribution/leap/15.4/appliances/openSUSE-Leap-15.4-Minimal-VM.x86_64-OpenStack-Cloud.qcow2.sha256
$ curl https://download.opensuse.org/$FILE
c686339ace6ab5d3cdf6999d00b3dec2b8adf11456f322d970d6caef74614381 openSUSE-Leap-15.4-Minimal-VM.x86_64-OpenStack-Cloud.qcow2
$ curl https://mirror.csclub.uwaterloo.ca/opensuse/$FILE
07a770c25f26a1b298e862c6b24096f80e0e4c37938cffa7f9261854eba15e7a openSUSE-Leap-15.4-Minimal-VM.x86_64-OpenStack-Cloud.qcow2
$ curl https://mirror.its.dal.ca/opensuse/$FILE
07a770c25f26a1b298e862c6b24096f80e0e4c37938cffa7f9261854eba15e7a openSUSE-Leap-15.4-Minimal-VM.x86_64-OpenStack-Cloud.qcow2
So different mirrors have different images and different checksums:
$ FILE=distribution/leap/15.4/appliances/openSUSE-Leap-15.4-Minimal-VM.x86_64-OpenStack-Cloud.qcow2
$ curl -so uwaterloo.qcow2 https://mirror.csclub.uwaterloo.ca/opensuse/$FILE
$ curl -so opensuse.qcow2 https://downloadcontent.opensuse.org./$FILE
$ sha256sum uwaterloo.qcow2
07a770c25f26a1b298e862c6b24096f80e0e4c37938cffa7f9261854eba15e7a uwaterloo.qcow2
$ sha256sum opensuse.qcow2
c686339ace6ab5d3cdf6999d00b3dec2b8adf11456f322d970d6caef74614381 opensuse.qcow2
So at least the servers seem to be internally consistent, but I guess it means the images are being rebuilt with the same names, so these are not repeatable downloads and can't have a digest in the template.
@vmoutoussamy The "kvm" images lack support for cloud-init, so don't work for Lima. We need the "OpenStack-Cloud" flavour. So this image works:
But just as for Tumbleweed, there is no corresponding aarch64 image. I'm also somewhat surprised that the Leap 15.4 images seem to get rebuilt over time. I expected this for Tumbleweed, but for Leap I thought you would get a reproducible image and not a snapshot with an undetermined number of updates already applied. I guess I can see arguments both ways, so I guess I just want to confirm that this is a rolling release, and checksums are meaningless unless downloaded from the same mirror at the exact same time. |
Signed-off-by: Eduardo Mínguez <[email protected]>
Sorry, I went AFK for a few days. It should be sorted out now. Thanks! |
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.
Thanks
No description provided.