[Bugfix:System] Temporary restrict Virtualbox to 7.0#10964
Conversation
There was a problem hiding this comment.
Agree that pinning to a 7.0.x version of virtualbox while vagrant adds support for 7.1.x is a good fix. Vagrant doesn't recommend using beta builds https://developer.hashicorp.com/vagrant/docs/providers/virtualbox and it feels a little weird using a beta/dev snapshot since thats an image most developers will not be using. It also runs the risk of brew moving what version virtualbox@beta points to which might present this issue again
I think manually installing a 7.0x version would be a better method, its unfortunate brew can't be used since it weirdly doesn't have versions other than a latest, 6.x and a beta version https://formulae.brew.sh/cask/virtualbox#default.
Here is a method to install a specific version manually for the macos image:
- name: install virtual box 7.0
run: |
curl -LO https://download.virtualbox.org/virtualbox/7.0.10/VirtualBox-7.0.10-158379-OSX.dmg
hdiutil mount VirtualBox-7.0.10-158379-OSX.dmg
sudo installer -pkg /Volumes/VirtualBox/VirtualBox.pkg -target /
hdiutil unmount /Volumes/VirtualBox
- name: Test VirtualBox
run: |
vboxmanage --version
Example test run and full file
https://github.com/shailpatels/github-actions-test-repo/actions/runs/10952911503/job/30412322150
|
Related vagrant issue: |
|
Does it matter which verison of 7.0.x we use? The latest one that is working is .20, but I do not really know if one is better or not |
Thats the version I had locally so I used it to test with, looks like 7.2.0 is the latest in the 7.x releases so probably does make sense to use that updated test repo to use 7.2: https://github.com/shailpatels/github-actions-test-repo/actions/runs/10953267653/job/30413258995 |
|
https://github.com/Homebrew/homebrew-cask/blob/f8e1cd3a27f8190a0e6487fa8b8ce3f311975c2e/Casks/v/[email protected] |
|
triggered here |
shailpatels
left a comment
There was a problem hiding this comment.
Looks good - thanks for the quick updates!
IDzyre
left a comment
There was a problem hiding this comment.
I agree this is a good change, we should create either an issue or some sort of notes to keep checking back and seeing if 7.1 becomes more stable in the future, as looking through the changelog some of it's features might be useful in the future.
### What is the current behavior? <!-- List issue if it fixes/closes/implements one using the "Fixes #<number>" or "Closes #<number>" syntax --> https://github.com/Submitty/Submitty/actions/runs/10976669670 failed Similar to PR #10964 . "The Vagrant up github action is currently not working with the new VirtualBox 7.1 update. https://formulae.brew.sh/cask/virtualbox https://forums.virtualbox.org/viewtopic.php?t=112320&sid=7ac5fd1e5fa51bd37e24ceede0fa6a1d&start=15" ### What is the new behavior? Restricts the version to 7.0.20 currently testing [here](https://github.com/Submitty/Submitty/actions/runs/10978720929)
What is the current behavior?
The Vagrant up github action is currently not working with the new VirtualBox 7.1 update.
https://formulae.brew.sh/cask/virtualbox
https://forums.virtualbox.org/viewtopic.php?t=112320&sid=7ac5fd1e5fa51bd37e24ceede0fa6a1d&start=15
What is the new behavior?
Restricts the version to 7.0.20
currently working on my forked repo