You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I change the box_url later, it should begin checking the new location, not the old location the next time I vagrant up when it checks for an outdated box.
Actual behavior
No matter what you change the box_url to in Vagrantfile, it always uses the url it used to initially provision the box.
Steps to reproduce
Provision a box
Change where the json file exists in Vagrantfile
Run vagrant box outdated --debug and see that it still uses the old URL (also happens with vagrant up)
Details
The metadata_url file in ~/.vagrant.d/boxes/< some string >/ contains the original URL used to provision the box, and is never updated based on the new contents of an updated Vagrantfile.
The text was updated successfully, but these errors were encountered:
just for documentary reasons. I just had this issue with custom box urls, as well. I had to change the domain of the page hosting my own boxes.
The solution was not just to destroy the current Vagrant box but to remove all old box versions from the local Vagrant installation, too. After doing this Vagrant used the new box_url value of the VagrantFile.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked and limited conversation to collaborators
Feb 4, 2020
# for freeto subscribe to this conversation on GitHub.
Already have an account?
#.
Vagrant version
2.0.3
Host operating system
Windows
Guest operating system
Irrelevant
Vagrantfile
Expected behavior
If I change the box_url later, it should begin checking the new location, not the old location the next time I
vagrant up
when it checks for an outdated box.Actual behavior
No matter what you change the box_url to in Vagrantfile, it always uses the url it used to initially provision the box.
Steps to reproduce
vagrant box outdated --debug
and see that it still uses the old URL (also happens withvagrant up
)Details
The metadata_url file in ~/.vagrant.d/boxes/< some string >/ contains the original URL used to provision the box, and is never updated based on the new contents of an updated Vagrantfile.
The text was updated successfully, but these errors were encountered: