-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Vagrant does not look to manage state of the host machine well #7977
Comments
The vagrant version you use seems to be over 2 years old. Consider upgrading to the newest version? |
Even after the update, does not look that Vagrant manage it well. I am stopping to use it, too slow and too many issues when using VMWare. Currently I am on |
If there is a specific problem that you are encountering with Vagrant, please feel free to open a new issue. Thanks! |
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. |
Vagrant version
1.5.8
Host operating system
Mac OS Sierra
Guest operating system
Ubuntu 16.04
Expected behavior
after vagrant destroy, I expect that there are no ports ( specified in the port forwarding ) that are still in LISTEN mode
Actual behavior
some port remains in LISTEN mode, even if the virtual machine have been destroyed
The text was updated successfully, but these errors were encountered: