Docker Builds Repository Summary
|
This page only describes the repository structure for context and understanding. For instructions on using the repository to build an image, visit this page. |
In the docker-builds Github repository, we share our Dockerfiles and automation scripts used for building Ping product container images. You can use these scripts and supporting pieces found in the repository to build an image of your own locally. For example, you can use this process to build an image for an older version we no longer provide on Docker Hub.
The image build process at Ping uses the Docker multi-stage build process. Every product image is a thin product layer added on top of a prebuilt parent image that Ping provides — pingbase or pingbase-java (see Parent Images). The parent images bundle the base operating system and, for Java products, the JVM (BellSoft Liberica, JDK 17, 21, or 25 — 25 is the default). They are published to Docker Hub with floating OS-major tags and are signed with Cosign. Common scripts shared by all products live in the repository as plain build inputs and are copied into each image; there are no foundation or intermediate images to build.
As you explore the repository, you will find a directory for each product, each with a Dockerfile and supporting scripts that add the product layer on top of the parent image. The result is a complete product image for use in Kubernetes or another container orchestration environment, with a consistent structure across all products.
Filesystem layout
The repository includes the following directories. This list is not comprehensive; it is focused on those folders of relevance to users:
Non-image related
| Repository Directory | Description |
|---|---|
ci_scripts |
Files and scripts used for building container images, both in an automated build pipeline and local use |
Image directories
| Repository Directory | Description |
|---|---|
ldap-sdk-tools |
Files and scripts for an image with LDAP SDK tools available for use with Ping Directory |
runtime |
Plain build inputs (not an image): common runtime scaffold — entrypoint chain, hook framework, dependency installation — copied into every product image |
legal |
Shared license text copied into every product image |
pingaccess |
Product-specific files and scripts for PingAccess container image |
pingauthorize |
Product-specific files and scripts for PingAuthorize container image |
pingauthorizepap |
Product-specific files and scripts for PingAuthorize Policy Editor container image |
pingcentral |
Product-specific files and scripts for PingCentral container image |
pingdataconsole |
Product-specific files and scripts for Ping Data Console container image |
pingdatasync |
Product-specific files and scripts for PingDataSync container image |
pingdelegator |
Product-specific files and scripts for PingDelegator container image |
pingdirectory |
Product-specific files and scripts for PingDirectory container image |
pingdirectoryproxy |
Product-specific files and scripts for PingDirectory Proxy container image |
pingfederate |
Product-specific files and scripts for PingFederate container image |
pingtoolkit |
Files and scripts for a utility image, typically used for an init or task-related container |