beckermj/vaguerent
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix link anchors

Browse Source
This commit is contained in:
Chris Roberts 2023-09-28 17:29:06 -07:00
parent 0d05b41536
commit fb5d004241
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
website/content/vagrant-cloud/boxes/architecture.mdx
View File

@ -40,7 +40,7 @@ hashicorp/precise
The Vagrant CLI (starting with version 2.4.0) will automatically match the
provider architecture using the detected local host architecture. If the
Vagrant CLI cannot find a matching architecture, it will attempt a
[special case match](/vagrant/vagrant-cloud/boxes/architecture#special-case-unknown-architecture).
[special case match](/vagrant/vagrant-cloud/boxes/architecture#unknown-architecture).
# Default Architecture
@ -94,7 +94,7 @@ will use the default architecture flag.
### User Requested
If the user sets the [config.vm.box_architecture](/vagrant/docs/vagrantfile/machine_settings#box_architecture)
If the user sets the [config.vm.box_architecture](/vagrant/docs/vagrantfile/machine_settings#config-vm-box_architecture)
option in their Vagrantfile to `nil`, the Vagrant CLI will use the
provider which has been flagged as the default architecture.
@ -102,7 +102,7 @@ provider which has been flagged as the default architecture.
The architecture value `unknown` combined with the default architecture
flag provides a special matching case for the Vagrant CLI. If the
[config.vm.box_architecture](/vagrant/docs/vagrantfile/machine_settings#box_architecture)
[config.vm.box_architecture](/vagrant/docs/vagrantfile/machine_settings#config-vm-box_architecture)
option in the local Vagrantfile is configured with the default `:auto`
value, and no architecture matching the host platform can be found
for the desired provider, the Vagrant CLI will check for a matching