ubuntu/eoan64 box does not contain guest additions
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-images |
New
|
Undecided
|
John Chittum |
Bug Description
https:/
Recently I attempted to upgrade Vagrant box Ubuntu version from 19.04 to 19.10 https:/
it gets the following error due to missing Virtualbox guest additions.
Current workaround is installing `vagrant-vbguest` vagrant plugin.
* Error with Ubuntu 10.10
```
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'ubuntu/eoan64'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'ubuntu/eoan64' version '20191031.0.0' is up to date...
==> default: Setting the name of the VM: rails-dev-
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 3000 (guest) => 3000 (host) (adapter 1)
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key
default: Warning: Connection reset. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default:
default: Vagrant insecure key detected. Vagrant will automatically replace
default: this with a newly generated keypair for better security.
default:
default: Inserting generated public key within guest...
default: Removing insecure key from the guest if it's present...
default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
default: No guest additions were detected on the base box for this VM! Guest
default: additions are required for forwarded ports, shared folders, host only
default: networking, and more. If SSH fails on this machine, please install
default: the guest additions and repackage the box to continue.
default:
default: This is not an error message; everything may continue to work properly,
default: in which case you may ignore this message.
==> default: Setting hostname...
==> default: Mounting shared folders...
default: /vagrant => /home/yahonda/
Vagrant was unable to mount VirtualBox shared folders. This is usually
because the filesystem "vboxsf" is not available. This filesystem is
made available via the VirtualBox Guest Additions and kernel module.
Please verify that these guest additions are properly installed in the
guest. This is not a bug in Vagrant and is usually caused by a faulty
Vagrant box. For context, the command attempted was:
mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant
The error output from the command was:
/sbin/mount.vboxsf: mounting failed with the error: No such device
```
* Vagrantfile
```
$ more Vagrantfile
# -*- mode: ruby -*-
# vi: set ft=ruby :
Vagrant.
config.vm.box = 'ubuntu/eoan64' # 19.10
config.
config.vm.network :forwarded_port, guest: 3000, host: 3000
config.
config.
v.memory = ENV.fetch(
v.cpus = ENV.fetch(
end
config.
end
$
```
* Workaround
```
$ vagrant plugin install vagrant-vbguest
Installing the 'vagrant-vbguest' plugin. This can take a few minutes...
Fetching: micromachine-
Fetching: vagrant-
Installed the plugin 'vagrant-vbguest (0.20.0)'!
$
```
description: | updated |
description: | updated |
tags: | added: id-5dd2cf798e62ed0cdf203dfc |
Changed in cloud-images: | |
assignee: | nobody → John Chittum (jchittum) |
This problem is also present in current boxes:
* `focal64` 20200116.1.0
* `eoan64` 20200114.0.0
It's blocking development for those versions of Ubuntu for me as it prevents creation of a local development environment with the local folder mounted inside the virtual machine.
For reference I am running: Ubuntur133883
* Ubuntu 18.04.3 LTS
* Vagrant 2.2.2
* Virtualbox 5.2.34_