mirror of https://github.com/containers/podman.git
improve document
Signed-off-by: chenkang <kongchen28@gmail.com>
This commit is contained in:
parent
728b73d7c4
commit
022bf589c8
|
@ -1228,14 +1228,12 @@ can override the working directory by using the **-w** option.
|
||||||
#### **\-\-pidfile**=*path*
|
#### **\-\-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)
|
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)
|
||||||
|
If the pidfile option is not specified, the container process' PID will be written to /run/containers/storage/${storage-driver}-containers/$CID/userdata/pidfile.
|
||||||
|
|
||||||
After the container is started, the location for the pidfile can be discovered with the following `podman inspect` command:
|
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 inspect --format '{{ .PidFile }}' $CID
|
||||||
podman run --pidfile $pidfilepath image
|
/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.
|
|
||||||
|
|
||||||
|
|
||||||
## EXAMPLES
|
## EXAMPLES
|
||||||
|
|
|
@ -1309,15 +1309,12 @@ can override the working directory by using the **-w** option.
|
||||||
#### **\-\-pidfile**=*path*
|
#### **\-\-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)
|
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)
|
||||||
|
If the pidfile option is not specified, the container process' PID will be written to /run/containers/storage/${storage-driver}-containers/$CID/userdata/pidfile.
|
||||||
|
|
||||||
After the container is started, the location for the pidfile can be discovered with the following `podman inspect` command:
|
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 inspect --format '{{ .PidFile }}' $CID
|
||||||
podman run --pidfile $pidfilepath image
|
/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.
|
|
||||||
|
|
||||||
|
|
||||||
## Exit Status
|
## Exit Status
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue