Question

我跟随Vagrant逐步跟踪official documentation CoreOS配置，当我执行命令vagrant up时，它会在阶段出现一些问题：配置和启用网络接口...... 。

输出：

devops@devops-server:~/workspace/coreos-vagrant$ vagrant up
Bringing machine 'core-01' up with 'virtualbox' provider...
==> core-01: Importing base box 'coreos-alpha'...
==> core-01: Matching MAC address for NAT networking...
==> core-01: Setting the name of the VM: coreos-vagrant_core-01_1406017161344_20671
==> core-01: Fixed port collision for 22 => 2222. Now on port 2200.
==> core-01: Clearing any previously set network interfaces...
==> core-01: Preparing network interfaces based on configuration...
    core-01: Adapter 1: nat
    core-01: Adapter 2: hostonly
==> core-01: Forwarding ports...
    core-01: 22 => 2200 (adapter 1)
==> core-01: Running 'pre-boot' VM customizations...
==> core-01: Booting VM...
==> core-01: Waiting for machine to boot. This may take a few minutes...
    core-01: SSH address: 127.0.0.1:2200
    core-01: SSH username: core
    core-01: SSH auth method: private key
    core-01: Warning: Connection timeout. Retrying...
    core-01: Warning: Connection timeout. Retrying...
==> core-01: Machine booted and ready!
==> core-01: Setting hostname...
==> core-01: Configuring and enabling network interfaces...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

mv /tmp/etcd-cluster.service /media/state/units/

Stdout from the command:



Stderr from the command:

mv: cannot move '/tmp/etcd-cluster.service' to '/media/state/units/': No such file or directory

我不知道问题是什么？

我在coreos vm上进行了身份验证，并且此计算机没有资源：/media/state/units/。 为什么？这很正常吗？

Answer 1

问题是我有旧版本的CoreOS，目前Beta版本367.1.0没有出现这些问题......然后我更新并且所有工作都成功了！。

感谢来自CoreOS-dev小组的@RobSzumski向我们展示了光明。

CoreOS：简单机器上的配置网络接口调用缺少的资源

1 个答案: