-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Vagrant doesn't work on Apple Silicon Macs because ubuntu/jammy64 is not an Arm image #6316
Comments
From random googling, it may be possible by changing the machine from eg. ubuntu/jammy64 to perk/ubuntu-2204-arm64 https://portal.cloud.hashicorp.com/vagrant/discover/perk/ubuntu-2204-arm64 There may also be bento boxes to allow for it. You might need to experiment a bit :-) |
Forgive me for the dumb question, but how do you change it? Simply replacing 'ubuntu/jammy64' with 'perk/ubuntu-2204-arm64' in
|
Add the following to your Vagrantfile before running vagrant up: ruby Update vagrant otherwise use this :- and re initialize |
I am following the instructions on this page: https://ardupilot.org/dev/docs/setting-up-sitl-using-vagrant.html
When I get to "vagrant up" step - it craps out due to the fact that Vagrant 2.4.1 doesn't support virtualbox Version 7.1.2 r164945 (Qt6.5.3). That can be fixed with the suggestion provided here: hashicorp/vagrant#13501
Once that is working, however, the fundamental problem is that the VM that it is trying to pull is built for the Intel architecture. Here is the full error message:
The same issue happens when I try to run the VM from the UI:
Would it be possible to support this?
Thank you!
The text was updated successfully, but these errors were encountered: