diff options
| author | OpenShift Merge Robot <openshift-merge-robot@users.noreply.github.com> | 2020-10-20 15:34:56 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-10-20 15:34:56 -0400 |
| commit | 4822cc8cabce33732cb210103aaa208f81102c5d (patch) | |
| tree | 366b14e2215e42ddbe7630be59b2e4bcde9b04b8 /docs/source/markdown/podman-play-kube.1.md | |
| parent | 6961b9475dbcbc6112d9c6022ac264c923ce083d (diff) | |
| parent | 3d2ad0f97a35617f76f30d02bbfa8aa1a7c1f958 (diff) | |
| download | podman-4822cc8cabce33732cb210103aaa208f81102c5d.tar.gz podman-4822cc8cabce33732cb210103aaa208f81102c5d.tar.bz2 podman-4822cc8cabce33732cb210103aaa208f81102c5d.zip | |
Merge pull request #8042 from rhatdan/tlsverify
--tls-verify and --authfile should work for all remote commands
Diffstat (limited to 'docs/source/markdown/podman-play-kube.1.md')
| -rw-r--r-- | docs/source/markdown/podman-play-kube.1.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/source/markdown/podman-play-kube.1.md b/docs/source/markdown/podman-play-kube.1.md index 00ee7c1df..97b0dc09a 100644 --- a/docs/source/markdown/podman-play-kube.1.md +++ b/docs/source/markdown/podman-play-kube.1.md @@ -20,7 +20,7 @@ Note: HostPath volume types created by play kube will be given an SELinux privat **--authfile**=*path* Path of the authentication file. Default is ${XDG\_RUNTIME\_DIR}/containers/auth.json, which is set using `podman login`. -If the authorization state is not found there, $HOME/.docker/config.json is checked, which is set using `docker login`. (Not available for remote commands) +If the authorization state is not found there, $HOME/.docker/config.json is checked, which is set using `docker login`. Note: You can also override the default path of the authentication file by setting the REGISTRY\_AUTH\_FILE environment variable. `export REGISTRY_AUTH_FILE=path` @@ -58,7 +58,7 @@ Directory path for seccomp profiles (default: "/var/lib/kubelet/seccomp"). (Not Require HTTPS and verify certificates when contacting registries (default: true). If explicitly set to true, then TLS verification will be used. If set to false, then TLS verification will not be used. If not specified, -TLS verification will be used unless the target registry is listed as an insecure registry in registries.conf. (Not available for remote commands) +TLS verification will be used unless the target registry is listed as an insecure registry in registries.conf. **--help**, **-h** |