使用Docker Provider的Vagrant因ssh上的rsync而失败

时间:2015-07-29 07:49:36

标签: ssh docker vagrant rsync boot2docker

使用Docker运行Vagrant时遇到问题。问题是共享文件夹的rsync。

WDFM32388067A:vagranttest d022051$ vagrant up
Bringing machine 'default' up with 'docker' provider...
==> default: Docker host is required. One will be created if necessary...
    default: Vagrant will now create or start a local VM to act as the Docker
    default: host. You'll see the output of the `vagrant up` for this VM below.
    default:  
    default: Importing base box 'hashicorp/boot2docker'...
    default: Matching MAC address for NAT networking...
    default: Checking if box 'hashicorp/boot2docker' is up to date...
    default: Setting the name of the VM: docker-host_default_1438155600426_39792
    default: Clearing any previously set network interfaces...
    default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
    default: Forwarding ports...
    default: 2375 => 2375 (adapter 1)
    default: 22 => 2222 (adapter 1)
    default: Running 'pre-boot' VM customizations...
    default: Booting VM...
    default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: docker
    default: SSH auth method: password
    default: Warning: Connection timeout. Retrying...
    default: Machine booted and ready!
==> default: Syncing folders to the host VM...
    default: Installing rsync to the VM...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

rsync --help

Stdout from the command:



Stderr from the command:

sh: rsync: not found

    default: The previous process exited with exit code 1.
    default: The previous process exited with exit code 1.

从错误消息中不清楚ssh或rsync是否是问题。也许是因为ssh超时了。我尝试了所有可能的ssh选项,但没有做任何事情。例如,我设置了config.ssh.private_key_path,但错误消息仍然完全相同。有没有人有类似的问题?

1 个答案:

答案 0 :(得分:2)

我还遇到了hashicorp / boot2docker。搬到mitchell / boot2docker也没有帮助,但我发现了

https://vagrantcloud.com/dduportal/boxes/boot2docker

运作良好(并且是最新的)。