-
Notifications
You must be signed in to change notification settings - Fork 24
Fedora Cloud Base Vagrant Image for Virtualbox Corrupted #160
Comments
Additionally, I just noticed that a vmdk is available directly here (mirrors.rit.edu):
As a test I will also download the vmdk directly today and see if it has the same issue as the bundled vagrant vmdk in the box archive. While writing this followup comment I noticed that the vmdk linked directly in this comment does have the same size as detailed the checksum:
Downloading the vmdk directly does appear to at least be giving me a file with the same size listed within the image checksum |
Quick update - direct VMDK download that is 737 M in size boots fine and has the correct checksum as expected/that is listed in Fedora-Cloud-32-1.6-x86_64-CHECKSUM. It would appear to me given the knowledge I have that the issue described occurs when building the vagrant box or perhaps with other failed step(s) leading up to gathering the components required with building the vagrant box. |
Downloaded https://download.fedoraproject.org/pub/fedora/linux/releases/32/Cloud/x86_64/images/Fedora-Cloud-Base-Vagrant-32-1.6.x86_64.vagrant-virtualbox.box
SHA256 checksum is the same as website after checking the file Fedora-Cloud-Base-Vagrant-32-1.6.x86_64.vagrant-virtualbox.box and box archive has no errors
The VMDK file within the box archive does not have the same SHA256 checksum as website. The checksum is B9232224AAB5E64D8BB2494239ECCCA1A84D5C6EA316998E79391866113F743C when I test the Fedora-Cloud-Base-Vagrant-32-1.6.x86_64.vmdk file locally (after extracted from box archive) rather than 39e8fe0062ae88714c5717ffa656f3c8ab1275a96d9802b742213faf17a6d502 (listed here: https://getfedora.org/static/checksums/Fedora-Cloud-32-1.6-x86_64-CHECKSUM).
Files downloaded were linked from https://alt.fedoraproject.org/cloud/. I have not yet discovered if there is another location to download vmdk file directly. In the meantime, it would be helpful if there another location to download the vmdks directly.
The text was updated successfully, but these errors were encountered: