opensource/podman
1
0
Fork 0
mirror of https://github.com/containers/podman.git synced 2025-07-15 03:02:52 +08:00
Code Issues Packages Projects Releases Wiki Activity

Order checkpoint options in man page alphabetically

Browse Source 
This just reorders the options in the podman-container-checkpoint man
page alphabetically. No actual content changed.

Signed-off-by: Adrian Reber <areber@redhat.com>
This commit is contained in:
Adrian Reber
2021-06-04 13:43:43 +00:00
committed by Adrian Reber
parent 5a209b3d76
commit 10875a67e4
1 changed files with 22 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files

44
docs/source/markdown/podman-container-checkpoint.1.md
View File

@ -10,32 +10,10 @@ podman\-container\-checkpoint - Checkpoints one or more running containers
Checkpoints all the processes in one or more containers. You may use container IDs or names as input. Checkpoints all the processes in one or more containers. You may use container IDs or names as input.
## OPTIONS ## OPTIONS
#### **--keep**, **-k**
Keep all temporary log and statistics files created by CRIU during checkpointing. These files
are not deleted if checkpointing fails for further debugging. If checkpointing succeeds these
files are theoretically not needed, but if these files are needed Podman can keep the files
for further analysis.
#### **--all**, **-a** #### **--all**, **-a**
Checkpoint all running containers. Checkpoint all running containers.
#### **--latest**, **-l**
Instead of providing the container name or ID, checkpoint the last created container. (This option is not available with the remote Podman client)
#### **--leave-running**, **-R**
Leave the container running after checkpointing instead of stopping it.
#### **--tcp-established**
Checkpoint a container with established TCP connections. If the checkpoint
image contains established TCP connections, this options is required during
restore. Defaults to not checkpointing containers with established TCP
connections.
#### **--export**, **-e** #### **--export**, **-e**
Export the checkpoint to a tar.gz file. The exported checkpoint can be used Export the checkpoint to a tar.gz file. The exported checkpoint can be used
@ -56,11 +34,33 @@ This option must be used in combination with the **--export, -e** option.
When this option is specified, the content of volumes associated with When this option is specified, the content of volumes associated with
the container will not be included into the checkpoint tar.gz file. the container will not be included into the checkpoint tar.gz file.
#### **--keep**, **-k**
Keep all temporary log and statistics files created by CRIU during checkpointing. These files
are not deleted if checkpointing fails for further debugging. If checkpointing succeeds these
files are theoretically not needed, but if these files are needed Podman can keep the files
for further analysis.
#### **--latest**, **-l**
Instead of providing the container name or ID, checkpoint the last created container. (This option is not available with the remote Podman client)
#### **--leave-running**, **-R**
Leave the container running after checkpointing instead of stopping it.
#### **--pre-checkpoint**, **-P** #### **--pre-checkpoint**, **-P**
Dump the container's memory information only, leaving the container running. Later Dump the container's memory information only, leaving the container running. Later
operations will supersede prior dumps. It only works on runc 1.0-rc3 or higher. operations will supersede prior dumps. It only works on runc 1.0-rc3 or higher.
#### **--tcp-established**
Checkpoint a container with established TCP connections. If the checkpoint
image contains established TCP connections, this options is required during
restore. Defaults to not checkpointing containers with established TCP
connections.
#### **--with-previous** #### **--with-previous**
Check out the container with previous criu image files in pre-dump. It only works Check out the container with previous criu image files in pre-dump. It only works