For example, when running the Ping Identity DevOps pingdatagovernancepap Docker container, you could use the following command to ensure that the policy database is on the mounted volume in preparation for future versions of the image. The command:
  • Runs a pingdatagovernancepap Docker container named pap on host port 8443.
  • Uses the ~/.pingidentity/devops environment file to configure common environment variables. See
  • Bind mounts a customized options.yml file named custom-options.yml to the server root using the server profile capability. The host system server-profile folder must contain instance/custom-options.yml for this example to work correctly. See
  • Sets the PING_OPTIONS_FILE environment variable to tell setup to use custom-options.yml.
  • Bind mounts a volume that maps a policy database to /opt/db/
  • Sets the PING_H2_FILE environment variable to tell setup to use /opt/db/ for the policy database. The environment variable must exclude the .mv.db extension.

The Ping Identity DevOps Docker image documentation is frequently updated as new features are released. For the most recent instructions about running the Docker images, see

  • Run this command.
    Note: For proper communication between containers, create a Docker network using a command such as docker network create --driver <network_type> <network_name>, and then connect to that network with the --network=<network_name> option.
    $ docker run --network=<network_name> --name pap -p 8443:443 \
      --env-file ~/.pingidentity/devops \
      --volume /home/developer/pap/server-profile:/opt/in/ \
      --env PING_OPTIONS_FILE=custom-options.yml \
      --volume /home/developer/pap/ \
      --env PING_H2_FILE=/opt/db/Symphonic \

    The Docker image <TAG> used in the example is only a placeholder. For actual tag values, see Docker Hub (