Got it working. Apparently vagrant package only works, if the interface is called eth0. To test my theory i applied the kernel parameters described in https://amolkg.blogspot.com/ to change the interface name to eth0.
After that the box came up and was reachable. I don't know if this can be considered a bug. On Friday, 31 August 2018 12:01:24 UTC+2, Armin Hohenegger wrote: > > Hi, > > I have to create a custom vagrant box from a rhel 7.5 image. My virtual > box vm comes up normal and is reachable over the network. To ensure this I > created a ifcfg file for the the interface enp0s3 under > /etc/sysconfig/network-scripts > > ifcfg-enp0s3: > > STARTMODE="auto" > DEVICE="enp0s3" > BOOTPROTO="dhcp" > ONBOOT="yes" > > The disk created by the command "vagrant package" does not contain any > ifcfg files. I am not sure at which point they get deleted. As a result the > box is not reachable when started with vagrant up. > > my vagrant version is 2.0.3 . > > Does anyone have a idea whats could be the reason for this? > > > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/40864364-7808-4d0b-a321-c202ddf7b075%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
