You will need to modify the Dockerfiles here to suit your needs. The Dockerfiles are changing often as we find better ways to build these images for a wide range of requirements.
There are a few ways to build the Docker images:
-
Manually. Copy the relevant artifacts (example: openam.war) to the directory and run
docker build -t forgerock/openam openam. -
Use the build.sh shell script. This essentially the same as performing a manual build. The build.sh script is available for convenience.
Please refer to the DevOps Guide for more information.
You must log on to BackStage to download the relevant ForgeRock binaries. Place the binaries in the appropriate folder, renaming them as required (openam.war, openidm.zip, opendj.zip, openig.war )
If you want to use a major or minor release (AM 14.0.1, for example), log on to backstage.forgerock.com and download the appropriate binary. The binary should be placed in the Docker build directory (e.g. openam/) and should not have any version info (openam.war, not OpenAM-14.0.1.war).
These images are intended to be orchestrated together using Kubernetes. They depend on external volumes being mounted for secrets, configuration and persistent data. As such, they are not supported in non Kubernetes environments (docker compose, docker swarm, etc.)
The product images are built automatically (using Conatainer Builder) when a commit is made to ForgeOps. These images are pushed to https://bintray.com/forgerock.
The java and git images are available on the docker hub. They are built when a new commit is made to ForgeOps