You are viewing the development documentation for the Apereo CAS server. The functionality presented here is not officially released yet. This is a work in progress and will be continually updated as development moves forward. To view the documentation for a specific Apereo CAS server release, please choose an appropriate version. The release schedule is also available here.
Upon every release of the CAS software, docker images are tagged and pushed to the Apereo CAS repository on Docker Hub. Images can be pulled down via the following command:
1 docker pull apereo/cas:v[A.B.C]
[A.B.C] represents the image tag that is mapped to the CAS server version.
A dockerized CAS deployment simply is an existing CAS overlay project that is wrapped by Docker. The overlay project already includes an embedded container to handle the deployment of CAS. The overlay project also includes an embedded build tool so that builds and deployments of CAS would not require a separate step to download and configure choices.
The docker build is simply instructed to clone the CAS overlay project, use the embedded Maven
instance to package and build it and finally uses the embedded container to deploy the final
CAS web application. Once CAS is running, it will be available under ports
The docker images that are hosted on Docker Hub are mostly meant to be used as quickstarters and demos. You may also be able to use them as base images to add your customizations into the image. The image is built out of an existing CAS overlay. So your approach could simply be to point your Dockerfile to your overlay and build your own specific images based on the instructions listed here.