If you’ve ever developed a python application, you’ve probably installed your python dependencies in a virtualenv. A simple way to do so is:
# build a virtualenv virtualenv venv # activate the virtualenv source venv/bin/activate # install some dependencies pip install flask
Thanks to virtualenv your project dependencies are now isolated from your other projects and from the operating system packages. Simple, isn’t it?
Another way to locally isolate you project is to install your dependencies in a docker container (actually the best practice would be to use virtualenv in a docker container as described here: https://hynek.me/articles/virtualenv-lives).
In this use-case, you’ll want to store the python packages required by your application in a mounted folder to avoid re-installing them everytime you reset your container in development. In other words, you’ll want to store the python dependencies in a specific folder.
The first obvious solution to that is using the
-t, --target <dir> Install packages into <dir>. pip option.
However this option ends up being a trap. When using the
--target option the installer changes its behaviour in a non desirable way for us, and becomes incompatible with the
--upgrade option as described here: https://github.com/pypa/pip/issues/1489.
A better solution, in line with PEP 370, is to use the PYTHONUSERBASE environment variable. Cf. https://www.python.org/dev/peps/pep-0370/.
You just need to then use
pip install --user and your packages will be installed in a specific folder without any of the strange side-effects of the
Here is the detailed step-by-step solution.
Your docker-compose file should look like this:
# docker-compose.yml vendors: image: python:3 working_dir: /mnt volumes: - .:/mnt environment: PYTHONUSERBASE: /mnt/vendor command: pip install -r requirements.txt --user --upgrade server: image: python:3 working_dir: /mnt volumes: - .:/mnt ports: - '5000:5000' environment: PYTHONPATH: src PYTHONUSERBASE: /mnt/vendor command: python src/server.py
Install your vendors (do it twice just to check!):
docker-compose run --rm vendors
Run your app:
docker-compose up -d server
PYTHONUSERBASE is used to compute the path of the user site-packages directory. You should use it in pair with the pip
--user option to install python packages in a custom directory.