This repository has been archived by the owner on Dec 16, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 107
Vagrant on Linux failing to load due to permission error with the minon file? #238
Comments
Aha! Looks like this is a problem with newer Vagrants: |
s/newer/older. Ubuntu installs 1.7.4 Vagrant, but #180 moved us to 1.8.0. So this is user error on my part! |
Thanks for updating the wiki, I totally meant to add that after the PR landed but forgot! This bug was definitely a thorn in the side for a while. |
No problem! It was actually somewhat fortunate, as I wasn't in a huge rush today and it forced me to learn a lot about how Vagrant works :-) |
aneeshusa
added a commit
to aneeshusa/servo-saltfs
that referenced
this issue
Mar 8, 2016
Use the Vagrant.require_version helper documented here: https://www.vagrantup.com/docs/vagrantfile/vagrant_version.html Eliminates issues like servo#238.
bors-servo
pushed a commit
that referenced
this issue
Mar 24, 2016
…bergstrom Ensure Vagrant version is at least 1.8.0 Use the Vagrant.require_version helper documented here: https://www.vagrantup.com/docs/vagrantfile/vagrant_version.html Eliminates issues like #238. Heads up: I didn't test this with a Vagrant older than 1.8.0, so I have no idea if this actually works. @larsbergstrom can you test this if possible since you ran into this? I want to make sure this is actually a useful change. <!-- Reviewable:start --> [<img src="https://reviewable.io/review_button.svg" height="40" alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/saltfs/240) <!-- Reviewable:end -->
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
@aneeshusa Do you have any idea why this might be failing when I attempt to
vagrant up
a new machine and how to fix it?The text was updated successfully, but these errors were encountered: