-
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
[docker provider] boot2docker root fs is too small to be targeted by docker provider' rsync #3680
Comments
+1 Just ran into this problem, there's a much larger partition at /mnt/sda/var/lib/docker |
@flevour I found a nifty easter egg at https://github.com/mitchellh/vagrant/blob/f475df0987d4195b0433273b61109161185c4190/plugins/providers/docker/action/host_machine_sync_folders.rb#L112 that allows you to override the intermediate path. Here's my new config that uses the larger partition.
Since this is undocumented I assume it could disappear in some future release. |
Fixed, we just put data in |
Looks like this might still be an issue in |
I have this issues too. Can this be reopened? The configuration above doesn't work:
|
It should be fixed in Vagrant 1.6.1. What vagrant version are you using? |
|
Ah, this must be exactly the issue @pauljz was mentioning above. |
It hangs on my development.log which has 893M. I can remove it and it works, but still... |
See #3771 |
I confirm, there are always two syncs (OSX). |
I have the same issue in Vagrant 1.6.3. Can you please reopen the issue? Changing /mnt/ to /var/lib/docker seems to fix the issue, so maybe you should change it to be default behaviour. Boot2docker is so convenient to use on OSX |
Same problem, also on vagrant 1.6.3, and it was also solved by changing new_build_dir replacing /mnt for /var/lib/docker, maybe there should be a variable for new_build_dir at least. |
I'd also suggest to re-open this issue, since it persists with 1.6.5 on OS X. I tried to hack vagrant with:
and it starts building from the Dockerfile and triggering apt-get. I get this error afterwards, but it seems to be another isssue...
|
In the transcript below I create a sample project with contains a big file which would get rsynced to boot2docker.
The rsync fails because it hasn't enough space to write in
/
.The text was updated successfully, but these errors were encountered: