Quantcast
Channel: Active questions tagged vagrant - DevOps Stack Exchange
Viewing all articles
Browse latest Browse all 64

getting error when trying to spin a vm using vagrant , is this issue with the box?

$
0
0

Getting this error when trying to spin a new vm using vagrant:

>vagrant up swarm-masterBringing machine 'swarm-master' up with 'virtualbox' provider...==> swarm-master: Box 'GospodinovM/ubuntu-18.04-minimal' could not be found. Attempting to find and install...    swarm-master: Box Provider: virtualbox    swarm-master: Box Version: >= 0==> swarm-master: Loading metadata for box 'GospodinovM/ubuntu-18.04-minimal'    swarm-master: URL: https://vagrantcloud.com/GospodinovM/ubuntu-18.04-minimal==> swarm-master: Adding box 'GospodinovM/ubuntu-18.04-minimal' (v0.0.1) for provider: virtualbox    swarm-master: Downloading: https://vagrantcloud.com/GospodinovM/boxes/ubuntu-18.04-minimal/versions/0.0.1/providers/virtualbox.box    swarm-master:==> swarm-master: Successfully added box 'GospodinovM/ubuntu-18.04-minimal' (v0.0.1) for 'virtualbox'!==> swarm-master: Importing base box 'GospodinovM/ubuntu-18.04-minimal'...==> swarm-master: Matching MAC address for NAT networking...==> swarm-master: Setting the name of the VM: docker-swarm-networking_swarm-master_1641130898918_54205==> swarm-master: Fixed port collision for 22 => 2222. Now on port 2200.==> swarm-master: Clearing any previously set network interfaces...==> swarm-master: Preparing network interfaces based on configuration...    swarm-master: Adapter 1: nat    swarm-master: Adapter 2: bridged    swarm-master: Adapter 3: hostonly==> swarm-master: Forwarding ports...    swarm-master: 22 (guest) => 2200 (host) (adapter 1)==> swarm-master: Running 'pre-boot' VM customizations...==> swarm-master: Booting VM...==> swarm-master: Waiting for machine to boot. This may take a few minutes...    swarm-master: SSH address: 127.0.0.1:2200    swarm-master: SSH username: vagrant    swarm-master: SSH auth method: private key    swarm-master:    swarm-master: Vagrant insecure key detected. Vagrant will automatically replace    swarm-master: this with a newly generated keypair for better security.    swarm-master:    swarm-master: Inserting generated public key within guest...    swarm-master: Removing insecure key from the guest if it's present...    swarm-master: Key inserted! Disconnecting and reconnecting using new SSH key...==> swarm-master: Machine booted and ready!==> swarm-master: Checking for guest additions in VM...==> swarm-master: Setting hostname...==> swarm-master: 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 -f '/tmp/vagrant-network-entry-1641130967''/etc/netplan/50-vagrant.yaml'chown root:root '/etc/netplan/50-vagrant.yaml'chmod 0644 '/etc/netplan/50-vagrant.yaml'netplan applyStdout from the command:Stderr from the command:Traceback (most recent call last):  File "/usr/sbin/netplan", line 23, in <module>    netplan.main()  File "/usr/share/netplan/netplan/cli/core.py", line 50, in main    self.run_command()  File "/usr/share/netplan/netplan/cli/utils.py", line 186, in run_command    self.func()  File "/usr/share/netplan/netplan/cli/commands/apply.py", line 46, in run    self.run_command()  File "/usr/share/netplan/netplan/cli/utils.py", line 186, in run_command    self.func()  File "/usr/share/netplan/netplan/cli/commands/apply.py", line 174, in command_apply    subprocess.check_call(['udevadm', 'settle'])  File "/usr/lib/python3.6/subprocess.py", line 311, in check_call    raise CalledProcessError(retcode, cmd)subprocess.CalledProcessError: Command '['udevadm', 'settle']' returned non-zero exit status 1.

I am not sure if this is issue with box or what , I am also facing somewhat different issue with ubuntu/xenial64.I have 8GB ram on host machine


Viewing all articles
Browse latest Browse all 64

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>