-
Notifications
You must be signed in to change notification settings - Fork 148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hostfile on host not updated on destroy of a running machine #159
Comments
+2 here |
I can confirm it. |
Vagrant: 1.7.4
|
I have the same problem on OSX. Along with the
.. because it looks like it is trying to remove itself in both places (guest and host), but it just won't do anything. My guess was permission problems, though it does write on "vagrant up" so i don't think that is the case.
The entry remains. Vagrant: 1.8.1 |
Vagrant: 1.7.2
Hostmanager: 1.6.0
Provider: Virtualbox 4.3.30
Host OS: OSX 10.9.5
Guest OS: Ubuntu 14.04
On
vagrant up
, the hostfile entries are created on both host and guest, but onvagrant destroy
(without halt, suspend, or any other machine action), the entries are not removed from the host.The relevant lines from my Vagrantfile:
The text was updated successfully, but these errors were encountered: