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

Adapt vagrant network setup to dhcp #130

Closed
wants to merge 0 commits into from
Closed

Conversation

hennevogel
Copy link
Member

This should work for everybody and not conflict with random ip ranges. @kirushik what do you think?

@coveralls
Copy link

Coverage Status

Changes Unknown when pulling 1f804f0 on hennevogel:master into * on SUSE:master*.

@kirushik
Copy link
Contributor

It would be great to have this, but then we need a better way of adding Vagrant host to the better_errors middleware.
I was unable to figure out anything better than hardcode: https://leprosorium.ru/comments/1867892/#new

@hennevogel
Copy link
Member Author

I also have new problems with the network & directory sharing. The vagrant network situation seems pretty shaky...

@hennevogel
Copy link
Member Author

Rebuilding the VM did the trick

@kirushik
Copy link
Contributor

kirushik commented Apr 8, 2015

Yes, unfortunately that's also the issue for me recently.
I don't know if that's VirtualBox bug, or the image itself. vagrant up won't work after vagrant halt, can only be solved with vagrant destroy.

I'd like to change our virtualbox base image to eliminate the most obvious reason for such a bug, but there are no other 13.2-based images at the moment: https://atlas.hashicorp.com/boxes/search?utf8=%E2%9C%93&sort=&provider=&q=opensuse

@hennevogel
Copy link
Member Author

vagrant reload helps me sometimes...

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

Successfully merging this pull request may close these issues.

3 participants