summaryrefslogtreecommitdiff
path: root/docs/source/markdown
diff options
context:
space:
mode:
authorchenkang <kongchen28@gmail.com>2021-04-17 21:25:11 +0800
committerchenkang <kongchen28@gmail.com>2021-04-17 21:25:11 +0800
commit022bf589c8ee23783721038f7b9e536ac489add7 (patch)
tree5da1859cf9917ca3da623439b40575033c9bece7 /docs/source/markdown
parent728b73d7c4186f4f0f9431d84ec2c5883f38ff20 (diff)
downloadpodman-022bf589c8ee23783721038f7b9e536ac489add7.tar.gz
podman-022bf589c8ee23783721038f7b9e536ac489add7.tar.bz2
podman-022bf589c8ee23783721038f7b9e536ac489add7.zip
improve document
Signed-off-by: chenkang <kongchen28@gmail.com>
Diffstat (limited to 'docs/source/markdown')
-rw-r--r--docs/source/markdown/podman-create.1.md10
-rw-r--r--docs/source/markdown/podman-run.1.md11
2 files changed, 8 insertions, 13 deletions
diff --git a/docs/source/markdown/podman-create.1.md b/docs/source/markdown/podman-create.1.md
index 1ac5a3951..db9ff937b 100644
--- a/docs/source/markdown/podman-create.1.md
+++ b/docs/source/markdown/podman-create.1.md
@@ -1228,14 +1228,12 @@ can override the working directory by using the **-w** option.
#### **\-\-pidfile**=*path*
When the pidfile location is specified, the container process' PID will be written to the pidfile. (This option is not available with the remote Podman client)
-After the container is started, the location for the pidfile can be discovered with the following `podman inspect` command:
+If the pidfile option is not specified, the container process' PID will be written to /run/containers/storage/${storage-driver}-containers/$CID/userdata/pidfile.
- $ podman inspect --format '{{ .Config.CreateCommand }}' $CID
- podman run --pidfile $pidfilepath image
+After the container is started, the location for the pidfile can be discovered with the following `podman inspect` command:
-If the pidfile option is not specified, the container process' PID will be written to
-/run/containers/storage/${storage-driver}-containers/$CID/userdata/pidfile.
-The default pidfile location is not listed in the `podman inspect` output.
+ $ podman inspect --format '{{ .PidFile }}' $CID
+ /run/containers/storage/${storage-driver}-containers/$CID/userdata/pidfile
## EXAMPLES
diff --git a/docs/source/markdown/podman-run.1.md b/docs/source/markdown/podman-run.1.md
index 5285d9608..f84a5913c 100644
--- a/docs/source/markdown/podman-run.1.md
+++ b/docs/source/markdown/podman-run.1.md
@@ -1309,15 +1309,12 @@ can override the working directory by using the **-w** option.
#### **\-\-pidfile**=*path*
When the pidfile location is specified, the container process' PID will be written to the pidfile. (This option is not available with the remote Podman client)
-After the container is started, the location for the pidfile can be discovered with the following `podman inspect` command:
-
- $ podman inspect --format '{{ .Config.CreateCommand }}' $CID
- podman run --pidfile $pidfilepath image
+If the pidfile option is not specified, the container process' PID will be written to /run/containers/storage/${storage-driver}-containers/$CID/userdata/pidfile.
-If the pidfile option is not specified, the container process' PID will be written to
-/run/containers/storage/${storage-driver}-containers/$CID/userdata/pidfile.
-The default pidfile location is not listed in the `podman inspect` output.
+After the container is started, the location for the pidfile can be discovered with the following `podman inspect` command:
+ $ podman inspect --format '{{ .PidFile }}' $CID
+ /run/containers/storage/${storage-driver}-containers/$CID/userdata/pidfile
## Exit Status