container/podman
container/podman
1
0
Fork 0
mirror of https://github.com/containers/podman synced 2024-10-19 08:44:11 +00:00
Code Issues Packages Projects Releases Wiki Activity

Modify according to comments

Browse source 
Signed-off-by: chenkang <kongchen28@gmail.com>
This commit is contained in:
chenkang 2021-04-16 23:45:10 +08:00
parent f331c9445f
commit 80c1dd0651
No known key found for this signature in database
GPG key ID: A592F3AE7ECB096B
2 changed files with 19 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
docs/source/markdown/podman-create.1.md
View file

@ -149,6 +149,7 @@ Write the container ID to the file
#### **\-\-conmon-pidfile**=*path*
Write the pid of the `conmon` process to a file. `conmon` runs in a separate process than Podman, so this is necessary when using systemd to restart Podman containers.
(This option is not available with the remote Podman client)
#### **\-\-cpu-period**=*limit*
@ -1226,9 +1227,15 @@ can override the working directory by using the **-w** option.
#### **\-\-pidfile**=*path*
Write the pid of the container process to a file.
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:
The default pidfile is RunDir/pidfile.
$ 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.
The default pidfile location is not listed in the `podman inspect` output.
## EXAMPLES

12
docs/source/markdown/podman-run.1.md
View file

@ -167,6 +167,7 @@ Write the container ID to *file*.
#### **\-\-conmon-pidfile**=*file*
Write the pid of the **conmon** process to a file. As **conmon** runs in a separate process than Podman, this is necessary when using systemd to restart Podman containers.
(This option is not available with the remote Podman client)
#### **\-\-cpu-period**=*limit*
@ -1307,9 +1308,16 @@ can override the working directory by using the **-w** option.
#### **\-\-pidfile**=*path*
Write the pid of the container process to a file.
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.
The default pidfile location is not listed in the `podman inspect` output.
The default pidfile is RunDir/pidfile.
## Exit Status