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

Add workaround hint for current Vagrant and VirtualBox versions #199

Conversation

Menkalian
Copy link
Contributor

@Menkalian Menkalian commented Oct 30, 2024

Description

closes #198

I opted to not alter the slides, since this information is only relevant in the short term and in my opinion the slides should contain information that is valid in the longer term.

Checklist

  • I made sure that the markdown files are formatted properly.
  • I made sure that all hyperlinks are working.

Copy link
Contributor

@MakisH MakisH left a comment

Choose a reason for hiding this comment

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

I noticed the same issue, thanks for updating!

For VirtualBox 7.1, one needs Vagrant 2.4.2. This is released, but might not have reached all distributions yet (Ubuntu 22.04 got that today).

As an alternative, one can download the .gem file from the GitHub release and run gem install <file>.gem. This requires installing Ruby.

@MakisH MakisH merged commit 502e2d9 into Simulation-Software-Engineering:main Nov 5, 2024
2 checks passed
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.

Mention Workaround for Vagrant 2.4.1 and VirtualBox 7.1
2 participants