=> default: Clearing any previously set network interfaces. => default: Clearing any previously set forwarded ports. => default: Checking if box 'bento/ubuntu-16.04' is up to date. Output: C:\Users\AHL\workspace>vagrant upīringing machine 'default' up with 'virtualbox' provider.
DOWNLOAD UBUNTU 16.04 ON VIRTUALBOX WINDOWS 10
Host machine: Lenovo X1 Carbon, Windows 10.My technical setup and reference files are listed below. I have previously successfully started the hashicorp/precise32 and ubuntu/trusty64 Ubuntu boxes with the same vagrant configuration and the same Oracle VB and have not encountered this problem.Īny help is appreciated. Also, I should mention that there are no other VM's running at the time this error occurs.įrom the error log it seems obvious that there is an issue with the netowrk interface eth1, but what exactly the problem is, is unclear to me. To be clear, I can't really use this post ( vagrant up command giving error and eth1 not showing a resolvable ip address) since it suggests to comment out the public_network part of the vagrant configuration. both Ubuntu 16 boxes).Īs you will see in my Vagrantfile below, I have a simple setup for bento/ubuntu-16.04 and use private_network only. not bento) or use a public_network configuration.Īs reported in, this issue does not exist for ubuntu/trusty64 or ubuntu/wily64, but seems to be an issue for both ubuntu/xenial64 and bento/ubuntu-16.04 (i.e. However these issues relate to either xenial64 (i.e. Interestingly, there are already some posts online (mainly on GitHub, e.g.: ), but also on AskUbuntu ( ), StackOverflow ( vagrant up command giving error and eth1 not showing a resolvable ip address) and StackExchange ( ). After loading the image and running vagrant up, I got an error as reported below, which relates to the network configuration of the virtual box. Today I was planning to get the latest Ubuntu release into my virtual box using vagrant.
0 kommentar(er)
