Deploying TKS on Podman - dogtagpki/pki GitHub Wiki
|
Note
|
This page is still under construction. |
This document describes the process to deploy TKS container on Podman with PKI 11.6 or later.
Current limitations:
-
Replication is not yet supported (i.e. no scaling)
-
HSM is not yet supported
-
No security domain (i.e. other subsystems need to be set up manually)
-
Long startup time (due to certs import and instance creation)
Create a network for the containers, for example:
$ podman network create example
Alternatively, use an existing network.
To deploy the OCSP container, prepare the following files:
-
server.p12which contains:-
ca_signingcertificate (see Generating CA Signing Certificate) -
sslservercertificate and key (see Generating SSL Server Certificate)
-
-
sslserver.csrcertificate request
Then store the files in a location that will be mapped to the /certs folder in the TKS container.
See also:
Create a folder (e.g. conf) to store Tomcat and TKS configuration files.
This folder will be mapped into the /conf folder in the TKS container.
Create a folder (e.g. logs) to store Tomcat and TKS log files.
This folder will be mapped into the /logs folder in the TKS container.
Run the TKS container with the following command:
$ podman run \
--name tks \
--hostname tks.example.com \
--network example \
--network-alias tks.example.com \
-v $PWD/certs:/certs \
-v $PWD/conf:/conf \
-v $PWD/logs:/logs \
-d \
quay.io/dogtagpki/pki-tks:latest
Wait until the TKS service is running:
$ podman logs -f tks
If the TKS container is no longer needed, it can be removed with the following command:
$ podman rm -f tks