#Running linux on a mac how to
#Running linux on a mac for mac
#Running linux on a mac install
#Running linux on a mac software
#Running linux on a mac code

Apple Python and homebrew Python and the different types of pyenv pythons and different cpu archs add completely new sources of frustration and errors. M1 macs add a whole new world of crazy to Python. That free(): invalid pointer error completely stumped me, since it didn't come with a detailed enough stacktrace that I could figure out which dependency (I have a hunch it was caused by a C deopendency) was causing it, and I couldn't figure out debugging techniques from searching the internet. Self.fetch_command(subcommand).run_from_argv(self.argv)ДЇile '/usr/local/lib/python3.8/site-packages/django/core/management/base.py', line 354, in run_from_argvДЇile '/usr/local/lib/python3.8/site-packages/django/core/management/commands/runserver.py', line 61, in executeДЇile '/usr/local/lib/python3.8/site-packages/django/core/management/base.py', line 398, in executeДЇile '/usr/local/lib/python3.8/site-packages/django/core/management/commands/runserver.py', line 96, in handleДЇile '/usr/local/lib/python3.8/site-packages/django/core/management/commands/runserver.py', line 103, in runДЄn_with_reloader(self.inner_run, **options)ДЇile '/usr/local/lib/python3.8/site-packages/django/utils/autoreload.py', line 640, in run_with_reloader manage.py runserver 0.0.0.0:3000ДЇile '/usr/local/lib/python3.8/site-packages/django/core/management/_init_.py', line 419, in execute_from_command_lineДЇile '/usr/local/lib/python3.8/site-packages/django/core/management/_init_.py', line 413, in execute The I ran into this error on container startup: docker run -it -v '$(pwd):/app' vial_web python -i.

#Running linux on a mac install

inside a Docker container seemed to work for most packages - I upgraded to FROM python:3.9-buster as my base image and was able to run apt-get install python-psycopg2 to talk to PostgreSQL. Python dependencies using wheels such as psycopg2-binary failed to install. Getting things to work in Docker on an M1 is really, really hard.

#Running linux on a mac code

Not unique to remote macOS but this was the first time I used the VS Code Remote Development using SSH extension and it worked flawlessly - I gave it the IP address, username and password that I had used over SSH and I was able to edit files on the remote Mac in the same way I edit files on my local machine. When I tried to run Docker containers with mounted volumes I ran into an issue where a UI prompt displayed on the macOS desktop stating that Docker wanted access to my filesystem - another reason to run the first set of commands over VNC rather than SSH.Д®ventually I got to a point where docker run commands were safe to run via SSH instead of a terminal over VNC.

#Running linux on a mac for mac

These both needed to be done not over SSH.Дocker for Mac required Rosetta 2 - thankfully installing that is a case of running softwareupdate -install-rosetta - which for me only took a couple of seconds and displayed an error message which appeared not to matter at all, since Docker for Mac then started working fine. I then installed Docker using brew install -cask docker. Pasting in the installation command from did the trick. So be sure to open a terminal in the Screen Sharing app over VNC and run the install commands there. I ended up having to turn the machine off through the MacStadium web interface, waiting a while and then turning it back on again in order to clear the errors (a soft reboot didn't help).

#Running linux on a mac software

Installing Homebrew and DockerДЇirst, most important lesson: do not attempt to install these large pieces of software over SSH! Both of these had points within the install process that triggered desktop UI interactions of some sort, and trying to start them over SSH lead to a bewildering array of permission errors. For SSH, ssh and then entering the password did the trick. These worked for both VNC and SSH.ДЇor VNC, navigating to vnc://ip.address.here in Safari opened the macOS Screen Sharing app and prompted me to connect. The machine became available within a minute of me entering the card details, and gave me an IP address I could connect to plus an administrator account username and password. AWS haven't launched this yet (at least anywhere I could find it), and Scaleway were out of stock on their machines which you can rent by the day, so I tried using a $109/month M1 Mac Mini from MacStadium. Since I don't have an M1 Mac, I decided to rent one.

#Running linux on a mac how to

I was trying to figure out how to get a development environment for a Django project running inside Docker in a M1 Mac.

TLDR: Use platform: linux/amd64 in docker-compose.yml and your containers will probably work!

Simon WillisonвЂ™s TILs Running Docker on an M1 Mac Running Docker on an M1 Mac | Simon WillisonвЂ™s TILs