"The job for system-cloudinit@-var-tmp-hostname.yml.service failed because the resource limit was exceeded"

I am starting to use Rancher and Vagrant to create my local development environment. The steps I took:

  • I already have VirtualBox installed.
  • I download and install the Vagrant package for Linux using

    sudo rpm -i vagrant_1.7.2_x86_64.rpm 

Wandering version:

 vagran --version Vagrant 1.7.2 

I cloned a Rancher repo from GitHub:

 git clone git@github.com :rancherio/rancher.git 

Who has a tramp file. After execution:

 sudo vagrant up 

Which step where I get the error, I got the following:

 ==> 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. 

Then, when I switch to localhost: 8080, the Rancher user interface is not installed.

+5
source share
2 answers

I also encounter the same problem, then I configure "config.rb", change the update channel to stable, as shown below,

 $update_channel='stable' 

then destroy roaming cores again and again,

 $ vagrant destroy $ vagrant up 

Finally, the tramp works successfully ~

+7
source

See this GitHub issue caused by updating to systemd on CoreOS 709.0.0.

As mentioned in a small town, you can revert to the old version of CoreOS using the beta channel. Or you can wait for this stretch request to merge into stray kernels so that you can bind a specific version to use.

+1
source

All Articles