Question

Vagrant Rsync无法正常工作，并且出现以下错误：

$  vagrant.exe rsync-auto
==> default: Doing an initial rsync...
==> default: Rsyncing folder: /cygdrive/d/OS/vweb-project/project/web-project/
 => /web-project
==> default: Watching: D:/OS/vweb-project/project/web-project
C:/HashiCorp/Vagrant/embedded/gems/gems/listen-3.0.2/lib/listen/event/queue.rb:1
5: warning: toplevel constant Queue referenced by Thread::Queue
C:/HashiCorp/Vagrant/embedded/gems/gems/listen-3.0.2/lib/listen/event/loop.rb:16
: warning: toplevel constant Queue referenced by Thread::Queue
C:/HashiCorp/Vagrant/embedded/gems/gems/listen-3.0.2/lib/listen/event/loop.rb:38
: warning: toplevel constant Queue referenced by Thread::Queue

这是我的流浪档案：

$ cat Vagrantfile
ENV["VAGRANT_DETECTED_OS"] = ENV["VAGRANT_DETECTED_OS"].to_s + " cygwin"
# -*- mode: ruby -*-
# vi: set ft=ruby :

# All Vagrant configuration is done below. The "2" in Vagrant.configure
# configures the configuration version (we support older styles for
# backwards compatibility). Please don't change it unless you know what
# you're doing.
Vagrant.configure(2) do |config|

  config.ssh.insert_key = false

  # The most common configuration options are documented and commented below.
  # For a complete reference, please see the online documentation at
  # https://docs.vagrantup.com.

  # Every Vagrant development environment requires a box. You can search for
  # boxes at https://atlas.hashicorp.com/search.
  config.vm.box = "ubuntu/trusty64"

  # Disable automatic box update checking. If you disable this, then
  # boxes will only be checked for updates when the user runs
  # `vagrant box outdated`. This is not recommended.
  config.vm.box_check_update = false

  # Create a forwarded port mapping which allows access to a specific port
  # within the machine from a port on the host machine. In the example below,
  # accessing "localhost:8080" will access port 80 on the guest machine.
  config.vm.network "forwarded_port", guest: 80, host: 8585
  config.vm.network "forwarded_port", guest: 5432, host: 5432

  # Create a private network, which allows host-only access to the machine
  # using a specific IP.
  # config.vm.network "private_network", ip: "192.168.33.10"

  # Create a public network, which generally matched to bridged network.
  # Bridged networks make the machine appear as another physical device on
  # your network.
  # config.vm.network "public_network"

  # Share an additional folder to the guest VM. The first argument is
  # the path on the host to the actual folder. The second argument is
  # the path on the guest to mount the folder. And the optional third
  # argument is a set of non-required options.
  config.vm.synced_folder "./project/web-project", "/web-project", type: "rsync", rsync__args: ["--verbose", "--rsync-path='sudo rsync'", "--archive", "--delete", "-z"]

  # Provider-specific configuration so you can fine-tune various
  # backing providers for Vagrant. These expose provider-specific options.
  # Example for VirtualBox:
  #
  config.vm.provider "virtualbox" do |vb|
    # Display the VirtualBox GUI when booting the machine
    # vb.gui = true

    # Customize the amount of memory on the VM:
    vb.memory = 4096
    vb.cpus = 2
  end

  config.ssh.shell = "bash -c 'BASH_ENV=/etc/profile exec bash'"

  # View the documentation for the provider you are using for more
  # information on available options.

  # Define a Vagrant Push strategy for pushing to Atlas. Other push strategies
  # such as FTP and Heroku are also available. See the documentation at
  # https://docs.vagrantup.com/v2/push/atlas.html for more information.
  # config.push.define "atlas" do |push|
  #   push.app = "YOUR_ATLAS_USERNAME/YOUR_APPLICATION_NAME"
  # end

  # Enable provisioning with a shell script. Additional provisioners such as
  # Puppet, Chef, Ansible, Salt, and Docker are also available. Please see the
  # documentation for more information about their specific syntax and use.
  config.vm.provision "shell", inline: <<-SHELL
     sudo apt-get update
  #   sudo apt-get install -y apache2
  SHELL

  #Docker
  config.vm.provision "docker" do |d|
    #d.build_image "/vagrant/app"
  end
  #Docker-compose
  config.vm.provision :docker_compose, yml: "/web-project/docker-compose.yml", rebuild: true, run: "always"
end

我已经尝试了几种方法让它起作用，但似乎没有任何事情发生，只是我昨天得到这些东西的信息，但我不知道它今天不再工作了，我确信我没有做任何改变我的当地环境。

任何帮助都会非常感激。

*我使用的是Windows 7 - ＆gt; cygwin - ＆gt; vagrant 1.7.4 - ＆gt; Ubuntu的

由于

Answer 1

似乎是一个带有listen gem的issue - 将gem升级到3.0.3会解决问题（根据github评论）

正如我从vagrant latest code看到的那样，他们仍然指向3.0.2，我认为你应该针对该项目打开一个问题，将它们指向gem修复并要求他们升级。

与此同时，您可以尝试进行此更新并重建流浪者（如果有可能）

Vagrant Rsync不会在主机和来宾

1 个答案: