Docker and Plone for add-on development

pigeonflight · November 2, 2017, 11:53am

update 1: A few notes for those working with Docker:

Modify the Dockerfile provided by plone.docker (unless you don't need to)

plone/plone.docker/blob/master/5.0/5.0.8/alpine/Dockerfile

FROM python:2.7-alpine
MAINTAINER "Plone Community" http://community.plone.org

RUN addgroup -g 500 plone \
 && adduser -S -D -G plone -u 500 plone \
 && mkdir -p /plone /data/filestorage /data/blobstorage \
 && chown -R plone:plone /plone /data

ENV PLONE_MAJOR=5.0
ENV PLONE_VERSION=5.0.8
ENV PLONE_MD5=246788240851f48bc2f84289a3dc6480

LABEL plone.version=$PLONE_VERSION
LABEL os="alpine" os.version="3.4"

RUN apk add --no-cache --virtual .build-deps \
    curl \
    bzip2-dev \
    gcc \
    libc-dev \

This file has been truncated. show original

For my use case I slightly modified the file. For my usecase I modified my buildout.cfg to remove a lot of extras and created a docker.cfg file.

Then altered my buildout line in the Dockerfile to use docker.cfg instead of buildout.cfg

COPY docker.cfg /plone/instance/docker.cfg
... snip...
 && sudo -u plone LIBRARY_PATH=/lib:/usr/lib bin/buildout -v -c docker.cfg \

Beware of the pypi http vs https issue

Add this to your buildout.cfg/docker.cfg (or equivalent file)

index = https://pypi.python.org/simple

It fixes this issue: