-
Notifications
You must be signed in to change notification settings - Fork 3
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
[Bug?] The specified checksum type is not supported by Vagrant: SHA256 #95
Comments
Hi @bsdooby, I have never seen this error before. Can you maybe try following the official instructions of running with debugging enabled and share the logs and your Vagrant file and configuration? Then I can try to take a look. https://developer.hashicorp.com/vagrant/docs/other/debugging |
Will do. Thank you for your init. feedback. |
|
|
Also seeing this. I have a new workstation where I built machines on 18 June. config.vm.box = "baunegaard/win11pro-en" I do not see this. (I note that the checksum is uppercase but the supported are all lower case so I wonder if there's something that has added to a file a different case?) Vagrant 2.4.1 in all cases. |
Other vagrant distros (e.g. generic/ubuntu or similar) do not seem to have
this issue.
Yes, it seems to be a "casing" issue. Windows-specific build files?
…On Thu, Jun 27, 2024 at 10:15 PM PaulNacamuli ***@***.***> wrote:
Also seeing this. I have a new workstation where I built machines on 18
June.
I shared the same vagrantfile with a colleague and he gets this error.
Removing my cached downloads, I get the same error.
(I note that the checksum is uppercase but the supported are all lower
case so I wonder if there's something that has added to a file a different
case?)
—
Reply to this email directly, view it on GitHub
<#95 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACIWLMPUYI2K4HVETB2G7ELZJRXHFAVCNFSM6AAAAABJYVFSSWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJVGU4TOMBWG4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@bsdooby @PaulNacamuli thanks for the details. This is tracked in more detail at gusztavvargadr/packer#444 if you think. |
Dear Gusztáv ( @gusztavvargadr )
Thx for the update and your work/support.
…On Tue, Jul 2, 2024 at 8:03 PM Gusztáv Varga ***@***.***> wrote:
@bsdooby <https://github.com/bsdooby> @PaulNacamuli
<https://github.com/PaulNacamuli> thanks for the details. This is tracked
in more detail at gusztavvargadr/packer#444
<gusztavvargadr/packer#444> if you think.
—
Reply to this email directly, view it on GitHub
<#95 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACIWLMOOCQ7TSC77WWYPM5DZKLTOBAVCNFSM6AAAAABJYVFSSWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBTHE4DGOBZGY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@bsdooby the mentioned box (and all my other boxes) should be working again. I am closing this issue in favor of gusztavvargadr/packer#444, but please let me know if you encounter any additional issues. |
When I try to
vagrant up
from https://vagrantcloud.com/api/v2/vagrant/gusztavvargadr/visual-studio-2019-community-windows-10. I get the above error.This issue occurs on a Linux Slackware64 "-current", using Vagrant 2.4.1 and VirtualBox 7.0.19r163060. A few days ago, I installed a similiar setup (also from your repos), and the error did not occur (IIRC).
The text was updated successfully, but these errors were encountered: