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

Mention Workaround for Vagrant 2.4.1 and VirtualBox 7.1 #198

Closed
Menkalian opened this issue Oct 30, 2024 · 1 comment · Fixed by #199
Closed

Mention Workaround for Vagrant 2.4.1 and VirtualBox 7.1 #198

Menkalian opened this issue Oct 30, 2024 · 1 comment · Fixed by #199

Comments

@Menkalian
Copy link
Contributor

The latest versions of Vagrant (2.4.1) and VirtualBox (7.1) are incompatible to each other.
This is an open issue for vagrant: hashicorp/vagrant#13501

There exist workarounds to make them compatible (my personal preference is updating the VirtualBox provider to treat VBx 7.1 as VBx 7.0).

This workaround (or at least the known issue) should be mentioned in the slides and/or the relevant exercise. Otherwise many people might run into this issue when installing the latest versions of these tools.

@Menkalian
Copy link
Contributor Author

I will provide a PR with suggestions for these changes.

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 a pull request may close this issue.

1 participant