vagrant images do not provide unknown architecture, leading to more configuration needed to setup boxes #11

Closed
opened 2023-12-19 14:59:09 +00:00 by neil · 4 comments
Member

from mattermost:

	
lolal36405
09:56


Hello Neil. rockylinux/9 3.0.0 does not provide the unknown-architecture as with 2.0.0, so this will fail on windows: vagrant init --box-version 3.0.0 --minimal rockylinux/9


Neil Hanlon
09:57
hm.. it does not automatically know what architecture to get?


lolal36405
09:57
It looks like even I am on an amd64-architecture vagrant wants to download the unknown architecture.


Neil Hanlon
09:57
interesting. that feels like a bit of an unexpected behavior by Vagrant

but--I do remember that the 3.0.0 release is a bit different than the 2.0.0 w.r.t. architectures, as you say. I had assumed this wouldn't affect anyone


lolal36405
09:58
No, only if specified in the Vargrantfile: config.vm.box_architecture = "amd64" - but not when using vagrant init.
from mattermost: ``` lolal36405 09:56 Hello Neil. rockylinux/9 3.0.0 does not provide the unknown-architecture as with 2.0.0, so this will fail on windows: vagrant init --box-version 3.0.0 --minimal rockylinux/9 Neil Hanlon 09:57 hm.. it does not automatically know what architecture to get? lolal36405 09:57 It looks like even I am on an amd64-architecture vagrant wants to download the unknown architecture. Neil Hanlon 09:57 interesting. that feels like a bit of an unexpected behavior by Vagrant but--I do remember that the 3.0.0 release is a bit different than the 2.0.0 w.r.t. architectures, as you say. I had assumed this wouldn't affect anyone lolal36405 09:58 No, only if specified in the Vargrantfile: config.vm.box_architecture = "amd64" - but not when using vagrant init. ```
Author
Member

vagrant cloud changed the interface to allow for multiple architectures, but apparently this doesn't work as intended. even though I had the amd64 images set as 'Default provider architecture' in the release, vagrant appears to not care about this (or, maybe, some versions of vagrants?)

vagrant cloud changed the interface to allow for multiple architectures, but apparently this doesn't work as intended. even though I had the amd64 images set as 'Default provider architecture' in the release, vagrant appears to not care about this (or, maybe, some versions of vagrants?)
Author
Member
https://github.com/hashicorp/vagrant/issues/13312
Author
Member

Added unknown arch (with amd64 details) to 9.3 and 8.9 releases

Added unknown arch (with amd64 details) to 9.3 and 8.9 releases
Author
Member

fixed upstream

fixed upstream
neil closed this issue 2024-03-12 22:40:02 +00:00
Sign in to join this conversation.
No Label
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: sig_cloud/meta#11
No description provided.