#INSTALLING ANACONDA ON MAC M1 INSTALL#

It will create a Python 3.9 folder in your /Applications folder, deposit python3, idle3, etc in /usr/local/bin as links back to:

#INSTALLING ANACONDA ON MAC M1 INSTALL#

Next, you install Python 3.9.4 (universal) directly from (not using brew) - which is a normal macOS package installer. your Zsh shell dot file (~/.zshrc):Īnd then from the Terminal, run the following to make that PATH current: # Place the prodigy.json file in the PRODIGY_HOME folderĬOPY prodigy.json $/prodigy.jsonĪlso add the following prodigy.json file at the same level as the Dockerfile and environment.Start with modifying the PATH line in. # Author: Christopher Connolly, Dylan Vanmali ERROR: error while attempting to bind on address ('::1', 8080, 0, 0): cannot assign requested addressĭockerfile # Dockerfile for prodigy using conda so you can run on Apple M1. I had to make minor adjustments to fix the following bind issue that occurred on my machine. Thanks for the extremely useful Dockerfile! I especially love the volume trick you added so we don't need to keep firing up a new container RUN echo 'source activate myenv' > ~/.bashrc # Use bash as the shell and activate the environment on load # Make sure the environment is activated: # Make RUN commands use the new environment: # Place your linux-wheel (prodigy-1.8.36m.cp37m-linux_x86_64.whl) in same directoty as this dockerfile. Here is the dockerfile definition # Dockerfile for prodigy using conda so you can run on Apple M1. Comment out the models that you don't use for faster build.Įnvironment.yml - this will be used by condaĭockerfile - to build a docker image # The environment.yml file is as follows Note that this dockerfile build includes the spacy models and takes a while to download. ) the environment will be automatically loaded. The conda environment is loaded using the bash run control file such that each time a shell is launched (e.g. Here's a workaround to get Prodigy running on your shiny new device using Docker Preview for Apple M1, and also using miniconda3 to get the Prodigy wheel installed. If you accidentally mix up your terminals or venvs I think things may break in unexpected ways, so the conda setup with x86-only python may be easier to manage.

Then use the system /usr/bin/python3 to create a venv and install prodigy from there. Here's one tutorial on setting up a Terminal for x86. You can also do something similar by creating/using a terminal app that runs in emulation mode and being careful to install/run everything from this terminal. When you're working in this conda env, it should be just like working on an intel/x86_64 mac. Restart your terminal so that it updates the path/conda settings.Ĭreate a new conda env with python3.8 and activate it: conda create -n prodigy python=3.8 We do have native spacy OSX ARM64 packages on the conda-forge channel, and at some point there will hopefully be native spacy and prodigy wheels, but our build infrastructure doesn't support it yet.)

(You could also use miniforge or another conda installer. One relatively easy option to get python in emulation mode is to run everything in a conda env for OSX x86_64.

The *macosx_10_14_x86_64.whl wheels won't run natively on an ARM mac, but you can run OSX x86_64 applications in emulation mode.

Installing anaconda on mac m1