Public | Automated Build

Last pushed: a month ago
Short Description
Minimal Python 2 & 3 environment to run unit tests and deployments
Full Description

Python Runner for Docker

This image can be used to run a Python project (e.g. unit tests)
and install Python packages that require C-extensions.

The image consists of a base Debian jessie install,
with both Python 2.7, Python 3.4 and development packages added
to install projects such as: : Pillow, psycopg2, pylibmc,
lxml, cffi, reportlab.

Python system packages are kept to a minimum, with only
pip, setuptools, wheel and virtualenv installed system-wide.
A minimalistic git install is present too, to support pip install -e git+....

We use this docker image to install, unittest and deploy projects via GitLab.
All pip built wheels are stored in the /cache dir,
which is the default volume in GitLab where persistent storage is mounted.

Building the containers

.. code-block:: bash

docker build -t edoburu/python-runner:base base/
docker build -t edoburu/python-runner:ansible ansible/
docker build -t edoburu/python-runner:sphinx sphinx/
docker build -t edoburu/python-runner:wkhtmltopdf wkhtmltopdf/
docker tag edoburu/python-runner:base edoburu/python-runner:latest

Updating on dockerhub:

.. code-block:: bash

docker login
docker push edoburu/python-runner:base
docker push edoburu/python-runner:latest
docker push edoburu/python-runner:sphinx
docker push edoburu/python-runner:ansible
docker push edoburu/python-runner:wkhtmltopdf

Usage in GitLab

You can use the container in the .gitlab-ci.yml file:

.. code-block:: yaml

image: edoburu/python-runner:base

# The test build
  type: test
  - virtualenv env
  - source env/bin/activate
  - pip install -r src/requirements.txt
  - ./src/

The virtualenv is not really needed as the image is already clean.
However, it makes sure the packages are installed in the /build folder,
which makes it easier to debug failed builds later.


For deployment, you can use the other image types:

.. code-block:: yaml

# Deploy to test server
  image: edoburu/python-runner:ansible
  stage: deploy
  - export ANSIBLE_FORCE_COLOR=true
  - cd deployment
  - ansible-playbook deploy.yml --limit="$CI_BUILD_REF_NAME" --extra-vars="git_branch=$CI_BUILD_REF"
  - beta

# Export documentation
  image: edoburu/python-runner:sphinx
  stage: deploy
  - cd docs
  - make html
  - rsync -av --delete _build/html/ /exported/docs/$(basename $CI_PROJECT_DIR)

An easy way to make sure the Docker process can access SSH keys,
is by exposing them via a mounted volume.
For example, add to config.toml:

.. code-block:: INI

    executor = "docker"
    # ...

      # The default image, if none specified
      image = "edoburu/python-runner"

      # Make sure the image can't become root on the host machine
      # Accessed files must be owned by the user Docker runs as.
      privileged = false
      cap_drop = ["DAC_OVERRIDE"]

      # Share pip cache files, provide deployment key
      volumes = [
Docker Pull Command
Source Repository