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.

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

Closed
wants to merge 2 commits into from

Conversation

KushalP
Copy link

@KushalP KushalP commented Oct 1, 2013

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.

@kyleconroy
Copy link
Contributor

The /vagrant folder should already be linked to the current folder.

@KushalP
Copy link
Author

KushalP commented Oct 1, 2013

In my case it wasn't. I'm using vagrant 1.3.1.

@KushalP
Copy link
Author

KushalP commented Oct 1, 2013

Going to destroy and up my VM and see if it's consistent.

@KushalP
Copy link
Author

KushalP commented Oct 1, 2013

Yup. You're right. I must have done something wrong on my side.

@KushalP KushalP closed this Oct 1, 2013
@KushalP KushalP reopened this Oct 2, 2013
@KushalP
Copy link
Author

KushalP commented Oct 2, 2013

No, this change is actually required. There was just some NFS lag in my testing.

@crosbymichael
Copy link
Contributor

ping @mzdaniel

@KushalP
Copy link
Author

KushalP commented Oct 2, 2013

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.

@ghost ghost assigned mzdaniel Oct 10, 2013
@creack
Copy link
Contributor

creack commented Oct 10, 2013

@KushalP can you rebase?

@KushalP
Copy link
Author

KushalP commented Oct 13, 2013

@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.
@mzdaniel
Copy link
Contributor

@KushalP: I wasn't able to verify your claim.

daniel@delphy:/go/src/github.com/dotcloud/docker$ vagrant --version
Vagrant 1.3.1
daniel@delphy:/go/src/github.com/dotcloud/docker$ virtualbox --help
Oracle VM VirtualBox Manager 4.2.16
.
.
daniel@delphy:/go/src/github.com/dotcloud/docker$ cat > test
This is a test
daniel@delphy:/go/src/github.com/dotcloud/docker$ vagrant ssh
Welcome to Ubuntu 12.04 LTS (GNU/Linux 3.8.0-31-generic x86_64)

Documentation: https://help.ubuntu.com/
Welcome to your Vagrant-built virtual machine.
Last login: Mon Oct 14 23:16:40 2013 from 10.0.2.2
vagrant@precise64:$ cat /vagrant/test
This is a test
vagrant@precise64:
$ cat >/vagrant/test
Test 2
vagrant@precise64:~$ exit
logout
Connection to 127.0.0.1 closed.
daniel@delphy:/go/src/github.com/dotcloud/docker$ cat test
Test 2

@KushalP
Copy link
Author

KushalP commented Oct 15, 2013

@mzdaniel Okay. I'll close this for now as it seems specific to my machine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants