Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ubuntu-16.04 networking failed #586

Closed
rbas opened this issue May 5, 2016 · 3 comments
Closed

Ubuntu-16.04 networking failed #586

rbas opened this issue May 5, 2016 · 3 comments

Comments

@rbas
Copy link

rbas commented May 5, 2016

Hi,
configuration network interfaces failed.

==> default: Configuring and enabling network interfaces...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

/sbin/ifdown eth1 2> /dev/null

Stdout from the command:


Stderr from the command:

mesg: ttyname failed: Inappropriate ioctl for device
vagrant box update --box bento/ubuntu-16.04
Checking for updates to 'bento/ubuntu-16.04'
Latest installed version: 2.2.6
Version constraints: > 2.2.6
Provider: virtualbox

I checked interfaces in VM and eth1 is renamed to enp0s3

cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto enp0s3
iface enp0s3 inet dhcp
pre-up sleep 2
@legal90
Copy link
Contributor

legal90 commented May 5, 2016

Looks like duplicate of #585
Also related: #545 (comment)

This is the issue of Vagrant and it was fixed in hashicorp/vagrant#7159. Looking forward the next version of Vagrant (> 1.8.1) to be released.

@legal90 legal90 closed this as completed May 5, 2016
@amirkoklan
Copy link

when can we have the new version of Vagrant which has solved this issue ?
there is not a temporary workaround without a new update ?

@cheeseplus
Copy link
Contributor

You can manually apply the patch from the posted fix (that is what I did) which is super hacky but works. Or you can run vagrant from source. Either way, there isn't much we, the bento team, can do to get a release of Vagrant cut.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants