mirror of
https://github.com/containers/podman.git
synced 2026-03-13 08:01:19 +08:00
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:
@@ -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 system’s 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.
|
||||
|
||||
Reference in New Issue
Block a user