vagrant - " job for system-cloudinit@-var-tmp-hostname.yml.service失败,因为超出了配置的资源限制"

vagrant - " job for system-cloudinit@-var-tmp-hostname.yml.service失败,因为超出了配置的资源限制",第1张


  1. 我已经安装了VirtualBox。
  2. 我使用

    sudo rpm -i vagrant_1.7.2_x86_64.rpm  
  3. Vagrant版本:

    vagran --version  
    Vagrant 1.7.2  


    git clone  


    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 ''
    rancher: URL:
    ==> rancher: Adding box 'coreos-alpha' (v709.0.0) for provider: virtualbox
    rancher: Downloading:
    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:
    rancher: SSH username: core
    rancher: SSH auth method: private key
    rancher: Warning: Connection timeout. Retrying...
    rancher: Vagrant insecure key detected. Vagrant will automatically replace
    rancher: this with a newly generated keypair for better security.
    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。


    2 个答案:

    答案 0 :(得分:7)

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



    $ vagrant destroy
    $ vagrant up


    答案 1 :(得分:1)

    请参阅此GitHub issue,这是由CoreOS 709.0.0中systemd的更新引起的。

    与小镇一样,您可以使用测试版频道切换回旧版CoreOS。或者你可以等待这个this pull request合并为vagrant-coreos,这样你就可以固定一个特定的版本来使用。