Vagrant &引用;system-cloudinit@-var-tmp-hostname.yml.service的作业失败,因为超出了配置的资源限制;

Vagrant &引用;system-cloudinit@-var-tmp-hostname.yml.service的作业失败,因为超出了配置的资源限制;,vagrant,systemd,rancher,Vagrant,Systemd,Rancher,我开始利用牧场主和流浪者来创造我当地的发展环境。我已完成的步骤: 我已经安装了VirtualBox 我下载并安装了用于linux的Vagrant软件包 sudo rpm -i vagrant_1.7.2_x86_64.rpm 流浪版本: vagran --version Vagrant 1.7.2 我从GitHub克隆了Rancher回购协议: git clone git@github.com:rancherio/rancher.git 里面有流浪汉档案。执行后: sud

我开始利用牧场主和流浪者来创造我当地的发展环境。我已完成的步骤:

  • 我已经安装了VirtualBox
  • 我下载并安装了用于linux的Vagrant软件包

    sudo rpm -i vagrant_1.7.2_x86_64.rpm  
    
  • 流浪版本:

    vagran --version  
    Vagrant 1.7.2  
    
    我从GitHub克隆了Rancher回购协议:

    git clone git@github.com:rancherio/rancher.git  
    
    里面有流浪汉档案。执行后:

    sudo vagrant up  
    
    这是我得到错误的步骤,我得到:

    ==> rancher: Box 'coreos-alpha' could not be found. Attempting to find and install...
    rancher: Box Provider: virtualbox
    rancher: Box Version: >= 308.0.1
    ==> rancher: Loading metadata for box 'http://alpha.release.core-os.net/amd64-usr/current/coreos_production_vagrant.json'
    rancher: URL: http://alpha.release.core-os.net/amd64-usr/current/coreos_production_vagrant.json
    ==> rancher: Adding box 'coreos-alpha' (v709.0.0) for provider: virtualbox
    rancher: Downloading: http://alpha.release.core-os.net/amd64-usr/709.0.0/coreos_production_vagrant.box
    rancher: Calculating and comparing box checksum...
    ==> rancher: Successfully added box 'coreos-alpha' (v709.0.0) for 'virtualbox'!
    ==> rancher: Importing base box 'coreos-alpha'...
    ==> rancher: Matching MAC address for NAT networking...
    ==> rancher: Checking if box 'coreos-alpha' is up to date...
    ==> rancher: Setting the name of the VM:rancher_rancher_1434213461241_51852
    ==> rancher: Clearing any previously set network interfaces...
    ==> rancher: Preparing network interfaces based on configuration...
    rancher: Adapter 1: nat
    rancher: Adapter 2: hostonly
    ==> rancher: Forwarding ports...
    rancher: 8080 => 8080 (adapter 1)
    rancher: 22 => 2222 (adapter 1)
    ==> rancher: Running 'pre-boot' VM customizations...
    ==> rancher: Booting VM...
    ==> rancher: Waiting for machine to boot. This may take a few minutes...
    rancher: SSH address: 127.0.0.1:2222
    rancher: SSH username: core
    rancher: SSH auth method: private key
    rancher: Warning: Connection timeout. Retrying...
    rancher: 
    rancher: Vagrant insecure key detected. Vagrant will automatically replace
    rancher: this with a newly generated keypair for better security.
    rancher: 
    rancher: Inserting generated public key within guest...
    rancher: Removing insecure key from the guest if its present...
    rancher: Key inserted! Disconnecting and reconnecting using new SSH key...
    ==> rancher: Machine booted and ready!
    ==> rancher: Setting hostname...
    The following SSH command responded with a non-zero exit status.
    Vagrant assumes that this means the command failed!  
    
    systemctl start system-cloudinit@-var-tmp-hostname.yml.service  
    
    Stdout from the command:  
    
    
    
    Stderr from the command:
    
    Job for system-cloudinit@-var-tmp-hostname.yml.service failed because a configured resource limit was exceeded. See "systemctl status system-cloudinit@-var-tmp-hostname.yml.service" and "journalctl -xe" for details.  
    

    然后,当我转到localhost:8080时,没有安装Rancher UI。

    我也遇到了同样的问题, 然后我配置“config.rb”,将更新通道更改为稳定,如下所示

    $update_channel='stable'
    
    然后再摧毁流浪汉coreos

    $ vagrant destroy
    $ vagrant up
    
    最后,流浪者成功运行~

    看到这一点,这是由Coreos709.0.0中systemd的更新引起的


    就像smalltown提到的那样,您可以通过使用beta频道切换回旧版本的CoreOS。或者,您可以等待vagrant coreos将其合并,以便锁定要使用的特定版本。

    您是否可以登录到docker实例并在失败后执行
    systemctl status system cloudinit@-var tmp hostname.yml.service
    。我得到了以下信息:system-cloudinit@-var-tmp-hostname.yml.service Loaded:not found(原因:没有这样的文件或目录)活动:不活动(死)