python
A Docker image that contains just the basic tools with a Python environment. It’s main usage is within a continuous integration script.
Downloading
cappysan/python can be downloaded from GitLab:
docker pull registry.gitlab.com/cappysan/images/python:3.8
docker pull registry.gitlab.com/cappysan/images/python:3.9
docker pull registry.gitlab.com/cappysan/images/python:3.10
docker pull registry.gitlab.com/cappysan/images/python:3.11
docker pull registry.gitlab.com/cappysan/images/python:3.12
docker pull registry.gitlab.com/cappysan/images/python:3.13
Contents
This docker inherits from python:3.x-slim and adds:
- curl to be able to trigger webhooks 
- gettext to have envsubst to alter - Dockerfileon the fly (without using- Dockerbuild-args)
- docker-systemctl-replacement as a - SystemDsystemctl shim
- git to be able to read current repository 
- gron to be able to parse a JSON response 
- jq to be able to parse a JSON response 
- make to enable building - Dockerfilesvia- Makefile
- moreutils to have tools such as - sponge
- pipx to be able to install Python packages 
- pre-commit preinstalled for Python jobs 
- python3-tomli to be able to read - pyproject.toml
- python3-venv to be able to install Python packages. (deprecated in favor of - uv)
- rsync to be able to handle remote file repositories and merging 
- sphinx, and dependencies, preinstalled for Python jobs 
- uv as a unified - pip,- virtualenv,- pip-tools, …
- yq to be able to parse a YAML files 
This list is subject to change at any time. It is recommended that you include the appropriate commands (eg: apt-get install / pipx install) in your continuous integration setup to ensure these dependencies are present. In the best case, the installation will be a no-op.
Status
The status of the Docker image depends on the underlying Python version. Refer to: https://devguide.python.org/versions/
| image | status | 
|---|---|
| python:3.6 | deprecated, removed on 2025-09-06 | 
| python:3.7 | deprecated, removed on 2025-09-06 | 
| python:3.8 | deprecated, end-of-life: 2024-10 | 
| python:3.9 | end-of-life: 2025-10 | 
| python:3.10 | end-of-life: 2026-10 | 
| python:3.11 | end-of-life: 2027-10 | 
| python:3.12 | end-of-life: 2028-10 | 
| python:3.12 | end-of-life: 2029-10 | 
Usage
An example of cappysan/python:3.x usage in a GitLab CI:
job:
  image: registry.gitlab.com/cappysan/images/python:3.11
  stage: build
  script:
    - make check