Public | Automated Build

Last pushed: 2 years ago
Short Description
Docker container for building python based apps in a build server that can be deployed on marathon
Full Description


Docker image that's used to build python apps using heroku compatible python buildpack. We use herokuish to run them. This is meant to be run as part of the build process in GoCD. The generated artifacts will be deployed on marathon.


We expect the app material to be mounted on /app inside the container. After launching the container, the final slug tarball will be available as app.tar.gz inside the material folder.

# Assuming the material is checkout into app folder in PWD
$ docker run -e USER_ID="$(id -u $(whoami))" -e GROUP_ID="$(id -g $(whoami))" -v $PWD/app:/app ind9/python-stack


  • bin/pre_package - Run before the generating the slug tarball. Any changes to the directory structure will be reflected in the generated slug.


We need to do that id foo while doing docker run because else the mounted directory would have root files which GoCD can't delete or overwrite on the next run.

Docker Pull Command
Source Repository