In order to set-up the CI/CD #149, Docker containers with Poetry installed should be created. Having the maintenance over these images gives the control over futures behaviours. ## ~~Run directly without Poetry~~ Run directly on the Docker image With Python. Poetry is somehow using Python installed on the system. `virtualenvs.create false` ## ~~Pre-built images~~ - https://pythonspeed.com/articles/base-image-python-docker-images/ - https://hub.docker.com/r/nikaro/poetry - https://hub.docker.com/r/michalmazurek/python-poetry ## Own-built images - Based on official Python images: [Docker hub](https://hub.docker.com/_/python?tab=description), [git repository](https://github.com/docker-library/python) - [x] Install `poetry`, and `libsodium` - [x] Publish git repository here https://git.duniter.org/docker/python3/poetry - [x] Python images with Slim Debian is enough - [x] Buster + [Python version 3.5, 3.6, 3.7, and 3.8](https://hub.docker.com/_/python?tab=description) - [x] Publish built images on `https://registry.duniter.org/docker/python3/poetry/$PYTHON_VERSION:{tag,latest}` - https://about.gitlab.com/2016/05/23/gitlab-container-registry/ - https://docs.gitlab.com/ee/user/project/container_registry.html - [ ] `change: - only $PYTHON_VERSION/Dockerfile`: not working - [ ] Installing `pip install poetry --pre` fails on v3.8: - installing `gcc` and `libffi-dev` by-passes the issue - [ ] Redshift Runner fails building containers due to already existing docker image to build certain containers - https://stackoverflow.com/questions/44257172/gitlab-ci-cannot-link-to-a-non-running-container ## Later - [ ] Windows? - [ ] Could be used by DuniterPy if it uses Poetry