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.

Sign up for GitHub

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

Jump to bottom

Added some FAQs #17

Closed
wants to merge 1 commit into from
Closed

Added some FAQs #17

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions docs/FAQ.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,3 +38,22 @@ restarting VirtualBox services. On MacOS X:
On SUSE / Red Hat:

service vboxdrv restart

## Vagrant NetworkCollision on VirtualBox

INFO interface: Machine: error-exit ["Vagrant::Errors::NetworkCollision", "The specified host network collides with a non-hostonly network!\nThis will cause your specified IP to be inaccessible. Please change\nthe IP or name of your host only network so that it no longer matches that of\na bridged or non-hostonly network."]

Make sure you have only one host-only network configured to use 192.168.124.0/24 . If you have libvirt running, check that no libvirt network using 192.168.124.0/24 .

## Vagrant fails ssh error on VirtualBox

The following SSH command responded with a non-zero exit status.

If you are using the vagrant cloud box, make sure you are on the vagrantcloud branch.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure adding that FAQ to the vagrantcloud branch makes a lot of sense..

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It might because a) that's the default branch and b) I'll port it to the other main branch. See #16 for more details. However I'm not sure I want this particular question/answer in the FAQ at all.


## Vagrant can't ssh, I modified the network configuration in the yaml files

The IP ranges are not supposed to be modified. Please revert the change and try again.