Zaczynam używać Ranchera i Vagranta do tworzenia mojego lokalnego środowiska do rozwoju. Kroki, które zrobiłem:"Zadanie dla [email protected] nie powiodło się, ponieważ przekroczono skonfigurowany limit zasobów"
- Już miałem zainstalowany VirtualBox.
pobrać i zainstalować pakiet Vagrant dla Linux z
sudo rpm -i vagrant_1.7.2_x86_64.rpm
Vagrant wersja:
vagran --version
Vagrant 1.7.2
I sklonowany ranczera repo z GitHub:
git clone [email protected]:rancherio/rancher.git
Która ma plik Vagrant. Po wykonaniu:
sudo vagrant up
który jest krokiem w których pojawia się błąd, mam to:
==> 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 [email protected]
Stdout from the command:
Stderr from the command:
Job for [email protected] failed because a configured resource limit was exceeded. See "systemctl status [email protected]" and "journalctl -xe" for details.
Potem, gdy idę do localhost: 8080 nie jest zainstalowany żaden Rancher UI.
Możesz zalogować się do swojej instancji dokujacej i po awarii wykonać "systemctl status system-cloudinit @ -var-tmp-hostname.yml.service". – Braiam
Mam to: [email protected] Załadowano: nie znaleziono (Powód: brak takiego pliku lub katalogu) Aktywny: nieaktywny (martwy) – eduartua