-
Notifications
You must be signed in to change notification settings - Fork 16.5k
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 Working on Arm Machines #26860
Comments
Maybe this is just an extra page in the manual, not a PR? |
I wouldn't mind a PR, but I think the changes could be a little less intrusive. See my PR for adding Noble support (#26985) for an example of where the resize step is skipped. Basically after maximum compatability / not breaking existing behaviour. So changing ... also, why remove the ptrace lines? |
Feature request
It would be great if vagrant worked on newer arm based machines (Apple silicon, etc) as Virtualbox still doesn't have an arm64 release.
I was able to get it to work with Docker by doing the following. Would offer up a PR, but not sure how it would need to be integrated to keep the community happy.
Vagrantfile
and add QEMU compatible box aboveubuntu/jammy64
block:and change
ubuntu/jammy64
to not be primary:Tools/vagrant/initvagrant.sh
, comment out resize, and add tzdata command to avoid prompt caused in later script:and comment out ptrace lines:
The text was updated successfully, but these errors were encountered: