After shaving at least three seperate yaks, and configuring a monstrosity I got it all running! Here's some lessons I learned.ĭisclaimer: I am very much not a linux / ops / devops person. So over the next three days I dive into documentation, I frantically search the web for 'vagrant docker M1' and 'vagrant docker config' and 'vagrant docker network issue' and 'vagrant docker systemctl'. I'm in a bit of a pickle.īut! Never fear! I can see that Vagrant also supports Docker. The preferred alternative is a product by VMWare which also doesn't (yet) support Apple Silicon. It's unclear whether Virtualbox will ever support Apple Silicon. Virtualbox very much doesn't support Apple Silicon.

This application requires a service which is run using Vagrant on Virtualbox.

NPM installs everything fine, my python packages all install and both the backend and frontend are running, too easy! Then I hit an issue. So I sit there on my first day ready to get started. 'Wow' I thought, this will be seamless, incredible. I'd heard from the wider community that everything 'just works' on the M1, even though it's not an Intel chip. I've recently started at a new job, and I'm fortunate enough to have a new M1 Macbook Air.

Vmware player mac m1