Skip to content

Conversation

@ottok
Copy link
Contributor

@ottok ottok commented May 26, 2020

Related: #96, #122

@ottok ottok force-pushed the feature/virtualbox-version-check branch from 4e667db to d602883 Compare January 26, 2021 12:53
@ottok
Copy link
Contributor Author

ottok commented Jan 26, 2021

If we get the experience from VirtualBox 6.2, 6.3 etc that they always break the project template / Vagrant, then we should have this restriction in place to prevent users from accidentally running too new VirtualBox versions. Oracle has a tendency to ignore backwards compatibility, so this is a risk.

Right now it is not a problem, so to avoid bloating the code base I am not merging this in yet, and thus leaving it as WIP.

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.

2 participants