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
Provide a synced folder for the virtualbox provisioner #2062
Conversation
The |
In my case it wasn't. I'm using vagrant 1.3.1. |
Going to destroy and up my VM and see if it's consistent. |
Yup. You're right. I must have done something wrong on my side. |
No, this change is actually required. There was just some NFS lag in my testing. |
ping @mzdaniel |
For completeness, I just checked this against Vagrant 1.3.3 (I was on 1.3.1 previously) and upgraded to VirtualBox 4.2.18 and the same behaviour occurs across two different machines. |
@KushalP can you rebase? |
@creack rebased 👍 |
By default, spinning up a VM using the VirtualBox provisioner doesn't set a synced folder which means local development (beyond toying with docker commands) can't really happen. This fixes that and means local development can occur.
@KushalP: I wasn't able to verify your claim. daniel@delphy:/go/src/github.com/dotcloud/docker$ vagrant --version Documentation: https://help.ubuntu.com/ |
@mzdaniel Okay. I'll close this for now as it seems specific to my machine. |
By default, spinning up a VM using the VirtualBox provisioner doesn't
set a synced folder which means local development (beyond toying with
docker commands) can't really happen.
This fixes that and means local development can occur.