PARTIALLY TESTED: Add --tls-details, use it to affect libimage and the like

For remote operation, start the remote service with --tls-details:
using --tls-details on the client side will only affect client's
connection.

This should eventually include many more tests - track down all current
uses of libpod.Runtime.{SystemContext,imageContext,LibimageRuntime}.
That will come later

Signed-off-by: Miloslav Trmač <mitr@redhat.com>
This commit is contained in:
Miloslav Trmač
2026-02-07 01:14:50 +01:00
parent b9da144e2d
commit 13e1d5af4b
14 changed files with 563 additions and 0 deletions

View File

@@ -177,6 +177,15 @@ Path to a PEM file containing the certificate authority bundle to verify the ser
Path to a PEM file containing the TLS client certificate to present to the server. `--tls-key` must also be provided.
#### **--tls-details**=*path*
Path to a `containers-tls-details.yaml(5)` file, affecting TLS behavior throughout the program.
If not set, defaults to a reasonable default that may change over time (depending on systems global policy,
version of the program, version of the Go language, and the like).
Users should generally not use this option unless they have a process to ensure that the configuration will be kept up to date.
#### **--tls-key**=*path*
Path to a PEM file containing the private key matching `--tls-cert`. `--tls-cert` must also be provided.