tools: update virtualbox networking configuration #11561
Merged
+3
−3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
As of VirtualBox 6.1.28, host-only networks are restricted to `192.168.56.0/21` by default, so spinning up the Vagrant boxes with secondary networks fail with an error `E_ACCESSDENIED`. Update the IP configuration of the Vagrant boxes to fall within the allowed range so that we don't need to ask developers from the community to make VirtualBox configuration updates outside of their normal Vagrant use.
angrycub
approved these changes
Nov 24, 2021
|
I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As of VirtualBox 6.1.28, host-only networks are restricted to
192.168.56.0/21by default, so spinning up the Vagrant boxes with secondary networks fail with an errorE_ACCESSDENIED.Update the IP configuration of the Vagrant boxes to fall within the allowed range so that we don't need to ask developers from the community to make VirtualBox configuration updates outside of their normal Vagrant use.
(I ran into this myself but see also hashicorp/vagrant#12553)