Closed alexgit2k closed 5 months ago
Hi there. This has the host operating system listed as Linux and the guest operating system listed as Windows. However, the vagrant init
is setting up a Linux guest. Is this issue being encountered on Windows host systems?
@chrisroberts My mistake, corrected it now in the issue. Happens on a Windows-host with Linux-guests.
Thanks for the clarification. Closing as a dup of #13274 which is fixed by #13278. This comment includes a workaround. The 2.4.1 release will include the fix which will be out at the end of the week.
Cheers!
Thank you very much Chris! I can confirm that with the changes in #13278 it is now working:
amd64
-architecture: vagrant init --box-version 9.3.20231118 --minimal almalinux/9
unknown
-architecture: vagrant init --box-version 2004.01 --minimal centos/7
Description
One of the architecture can be selected as "Default provider architecture" which is then marked with a star on the frontend. If no architecture is supplied (like with
vagrant init
) it looks like vagrant wants to fetch the box for architectureunknown
and is not using the architecture which has been set as default.Alma Linux has no box for the
unknown
architecture, thereforevagrant init
is not working:Rocky Linux has a box for the
unknown
architecture, thereforevagrant init
is working:Expected behavior
Provisioned box.
Actual behavior
Reproduction information
Vagrant version
2.4.0
Host operating system
Windows 10
Guest operating system
Almalinux 9, Rocky Linux 9
Steps to reproduce
Not working
Working
Vagrantfile
Not working
Working