I am experiencing same issue, same debug output, have you found some work-around?
El jueves, 11 de septiembre de 2014, 19:02:27 (UTC-5), Gary Gutman escribió: > > Hi everyone, > > I am also having the same problem. I was wondering if anyone managed to > figure out the problem > > I am on Windows 7 SP1, using vagrant 1.6.3 and VBox 4.3.16. > > My vagrant file is as follows > > VAGRANTFILE_API_VERSION = "2" > > Vagrant.configure(VAGRANTFILE_API_VERSION) do |config| > config.vm.provider "docker" do |d| > d.image = "jenkins" > d.has_ssh = true > end > end > > I ran with debug enabled and these are the last few lines of the output. > > > ==> default: Syncing folders to the host VM... >> INFO machine: Calling action: sync_folders on provider VirtualBox >> (aefc7378-de3a-4c7b-b62f-c743ee5b8f1f) >> DEBUG environment: Attempting to acquire process-lock: >> machine-action-db2295e977cb9d103fb248d0808988f4 >> DEBUG environment: Attempting to acquire process-lock: dotlock >> INFO environment: Acquired process lock: dotlock >> INFO environment: Released process lock: dotlock >> INFO environment: Acquired process lock: >> machine-action-db2295e977cb9d103fb248d0808988f4 >> INFO environment: Released process lock: >> machine-action-db2295e977cb9d103fb248d0808988f4 >> INFO runner: Preparing hooks for middleware sequence... >> INFO runner: 2 hooks defined. >> INFO runner: Running action: #<Vagrant::Action::Builder:0x361d148> >> INFO warden: Calling IN action: >> #<Vagrant::Action::Builtin::SyncedFolders:0x36a27c8> >> INFO subprocess: Starting process: >> ["C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\/powershell.EXE", >> "-NoProfile", "-ExecutionPolicy", "Bypass", >> "$PSVersionTable.PSVersion.Major"] >> DEBUG subprocess: Selecting on IO >> DEBUG subprocess: stdout: 2 > > > > > > > On Monday, June 2, 2014 11:01:00 AM UTC-4, Adam Stallard wrote: >> >> Sorry to chime in, but I am having the same problem, also windows 7, >> using vagrant 1.6.3, also using the docker provider. I added this line to >> the Vagrantfile: >> >> config.vm.synced_folder ".", "/vagrant", type: "rsync" >> >> and it first tried complained that it couldn't find rsync in the path, so >> I installed rsync (for cygwin 64 bit), and then it went back to hanging >> again in the same place, same debug output. >> >> I changed the line in the Vagrantfile to say >> >> config.vm.synced_folder ".", "/vagrant", disabled: "true" >> >> and now it doesn't care whether or not rsync exists, but either way it >> will hang in the same place, same debug output. >> >> I really don't care about file syncing yet, so maybe Paul could tell me >> how he disabled file syncing for docker under windows. >> >> >> >> On Wednesday, May 14, 2014 2:23:03 PM UTC-7, Michael Sverdlik wrote: >>> >>> Try to manually specify rsync sync folder >>> <http://docs.vagrantup.com/v2/synced-folders/rsync.html> as a >>> workaround, see if that helps. You need to use rsync since boot2docker >>> image doesn't support VirtualBox Guest Additions. >>> >> -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/6eb32e5c-c77a-4431-bc32-9af0aca81021%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
