To be able to create our plone buildout fast and often, we base our other images on this one.
Plone buildout is based on plone test buildout version 5.0 (https://raw.github.com/collective/buildout.plonetest/master/plone-5.0.x.cfg).
Start the instance:
docker run -p 8080:8080 jfroche/plone:5.0
Access the instance on http://localhost:8080 using login admin / password admin.
To start the instance using volume
mkdir filestorage
mkdir blobstorage
docker run -p 8080:8080 -v $PWD/filestorage:/code/var/filestorage -v $PWD/blobstorage:/code/var/blobstorage jfroche/plone:5.0
You can reuse this image like this in your Dockerfile in your own buildout directory.
FROM jfroche/plone:5.0
COPY . /code/
USER root
RUN chown -R plone .
USER plone
RUN bin/buildout -Nv
Buildout is installed in /code
This will push your code in the container (with correct permissions) and start a buildout based on the buildout created in our image (cf https://github.com/jfroche/docker-plone/blob/5.0/buildout.cfg) and you will avoid downloading all plone packages.
To simplify even more your Dockerfile check the 5.0-onbuild branch (https://github.com/jfroche/docker-plone/tree/5.0-onbuild) or image (FROM jfroche/plone:5.0-onbuild) which use ONBUILD instructions (https://docs.docker.com/reference/builder/#onbuild).
This image is not meant for production. We are building other images based on Relstorage for that.
We speed up local build of this image using: https://github.com/silarsis/docker-proxy You might want to look at it for local build of your image (or use your own pypi mirror).
Content type
Image
Digest
sha256:18cd4d08d…
Size
312.8 MB
Last updated
almost 11 years ago
docker pull jfroche/docker-plone:4.3