-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
chef/fedora-21 #333
Comments
I believe Vagrant doesn't officially support Fedora 21 yet, therefore it doesn't know to rename the Ethernet interfaces from the driver name to |
No, I think it's a packaging issue. Please look at hashicorp/vagrant#1777 (comment) Regards, |
@Tcharl No, I don't think that's the issue, as the fedora-21 box doesn't have such a file in |
Ok, sorry for the mistake |
Temporary fix that will change the naming scheme of interfaces:
^^ use the new box now. All interfaces will now be eth0,eth1.. the old way that vagrant/vbox understand. |
Updates README to note Debian and Ubuntu support. Drops Fedora 20 hosts file due to issue at chef/bento#333
Updates README to note Debian and Ubuntu support. Drops Fedora 20 hosts file due to issue at chef/bento#333
Updates README to note Debian and Ubuntu support. Drops Fedora 20 hosts file due to issue at chef/bento#333
I've pushed an updated version of the box with the latest tools for each respective provider #428 and the issue no longer exists. |
Hello all,
I hope it will be relevant to report the bug I found here:
When I created a new
chef/fedora-21
virtualbox instance, the output was:So I switched to
chef/fedora-20
and it works properly.My configuration is:
I can use
chef/fedora-20
but I think it will be nice to fix it 👍Have a nice day !
The text was updated successfully, but these errors were encountered: