Vagrant bionic 64 with virtualbox image doesn't start network correctly

[Luis Ferro]

When starting the image box 'ubuntu/bionic64' (v20171206.0.0) for virtualbox in MacOS, I get this error:

    bash: line 4: /sbin/ifdown: No such file or directory
    sed: can't read /etc/network/interfaces: No such file or directory
    sed: can't read /etc/network/interfaces: No such file or directory
    bash: line 20: /sbin/ifup: No such file or directory

After entering into it with vagrant ssh, I notice that the /sbin/ifdown and corresponding /sbin/ifup are not installed by default.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Phillip Susi (psusi)]

Are you still seeing this today?

[Carsten Decker (conceptdeluxe)]

I have the same issue with 'ubuntu/bionic64' (v20180426.2.0) on MacOS 10.11 / Vagrant 1.9.8 / VirtualBox 5.1.30

---

The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

/sbin/ifdown 'enp0s8' || true
/sbin/ip addr flush dev 'enp0s8'
# Remove any previous network modifications from the interfaces file
sed -e '/^#VAGRANT-BEGIN/,$ d' /etc/network/interfaces > /tmp/vagrant-network-interfaces.pre
sed -ne '/^#VAGRANT-END/,$ p' /etc/network/interfaces | tac | sed -e '/^#VAGRANT-END/,$ d' | tac > /tmp/vagrant-network-interfaces.post

cat \
  /tmp/vagrant-network-interfaces.pre \
  /tmp/vagrant-network-entry \
  /tmp/vagrant-network-interfaces.post \
  > /etc/network/interfaces

rm -f /tmp/vagrant-network-interfaces.pre
rm -f /tmp/vagrant-network-entry
rm -f /tmp/vagrant-network-interfaces.post

/sbin/ifup 'enp0s8'

Stdout from the command:

Stderr from the command:

bash: line 4: /sbin/ifdown: No such file or directory
bash: line 20: /sbin/ifup: No such file or directory

---

[Carsten Decker (conceptdeluxe)]

I've just checked v20180518.0.0 with the same result.

[Phillip Susi (psusi)]

I think those commands and files are no longer installed by default and it looks like vagrant is still trying ot use them.

[Carsten Decker (conceptdeluxe)]

Yes, right - thank you!

This is related to:

https://wiki.ubuntu.com/MigratingToNetplan#Rationale

https://askubuntu.com/questions/1005390/why-did-ubuntu-change-the-network-configuration

https://github.com/hashicorp/vagrant/issues/9134

https://github.com/hashicorp/vagrant/issues/9428

As I can not upgrade to the latest Vagrant version due to other compatibility issues I'll try installing ifupdown package manually as a workaround.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Robert C Jennings (rcj)]

A backport of https://github.com/hashicorp/vagrant/pull/9338 could resolve this and allow bionic to launch Focal and later vagrant boxes.

[Helmo (helmo)]

A workaround is to download and install the deb file from https://www.vagrantup.com/downloads

Tested with 2.2.14