Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Caching: investigate catching shared folder failure and providing useful message #302

Open
cheeseplus opened this issue Mar 22, 2017 · 1 comment
Open

Caching: investigate catching shared folder failure and providing useful message #302

cheeseplus opened this issue Mar 22, 2017 · 1 comment
Assignees
@robbkidd
Labels
Improvement

Comments

@cheeseplus
Copy link
Contributor

If Vagrant barfs on loading the shared folders and we can reliably catch that message for the providers then we should print a nice message showing how to disable shared folders.

Even if they are using bento boxes there might be hypervisor vs vmtools incompatibilities that prevent the shared folder from mounting so this would at least provide a clear path forward for users.
@cheeseplus
Copy link
Contributor Author

Although I need to push the box to Vagrant Cloud, Debian 9.x vmware boxes currently break with shared folders and as such are a great test case.

@robbkidd robbkidd self-assigned this Jul 26, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@robbkidd robbkidd

Labels
Improvement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@robbkidd @cheeseplus