diff options
Diffstat (limited to 'docs/source/markdown')
| -rw-r--r-- | docs/source/markdown/podman-exec.1.md | 12 | ||||
| -rw-r--r-- | docs/source/markdown/podman-remote.1.md | 18 | ||||
| -rw-r--r-- | docs/source/markdown/podman-rm.1.md | 11 | ||||
| -rw-r--r-- | docs/source/markdown/podman-rmi.1.md | 11 | ||||
| -rw-r--r-- | docs/source/markdown/podman-run.1.md | 8 | ||||
| -rw-r--r-- | docs/source/markdown/podman-stop.1.md | 20 | ||||
| -rw-r--r-- | docs/source/markdown/podman.1.md | 18 | 
7 files changed, 52 insertions, 46 deletions
| diff --git a/docs/source/markdown/podman-exec.1.md b/docs/source/markdown/podman-exec.1.md index 8c0106d70..1bd10f9ba 100644 --- a/docs/source/markdown/podman-exec.1.md +++ b/docs/source/markdown/podman-exec.1.md @@ -80,28 +80,28 @@ when creating the container.  The exit code from `podman exec` gives information about why the command within the container failed to run or why it exited.  When `podman exec` exits with a  non-zero code, the exit codes follow the `chroot` standard, see below: -**_125_** if the error is with Podman **_itself_** +  **125** The error is with Podman itself      $ podman exec --foo ctrID /bin/sh; echo $?      Error: unknown flag: --foo      125 -**_126_** if the **_contained command_** cannot be invoked +  **126** The _contained command_ cannot be invoked      $ podman exec ctrID /etc; echo $?      Error: container_linux.go:346: starting container process caused "exec: \"/etc\": permission denied": OCI runtime error      126 -**_127_** if the **_contained command_** cannot be found +  **127** The _contained command_ cannot be found      $ podman exec ctrID foo; echo $?      Error: container_linux.go:346: starting container process caused "exec: \"foo\": executable file not found in $PATH": OCI runtime error      127 -**_Exit code_** of **_contained command_** otherwise +  **Exit code** The _contained command_ exit code -    $ podman exec ctrID /bin/sh -c 'exit 3' -    # 3 +    $ podman exec ctrID /bin/sh -c 'exit 3'; echo $? +    3  ## EXAMPLES diff --git a/docs/source/markdown/podman-remote.1.md b/docs/source/markdown/podman-remote.1.md index bbc54a2a6..eab2405b2 100644 --- a/docs/source/markdown/podman-remote.1.md +++ b/docs/source/markdown/podman-remote.1.md @@ -65,27 +65,27 @@ The exit code from `podman` gives information about why the container  failed to run or why it exited.  When `podman` commands exit with a non-zero code,  the exit codes follow the `chroot` standard, see below: -**_125_** if the error is with podman **_itself_** +  **125** The error is with podman itself      $ podman run --foo busybox; echo $?      Error: unknown flag: --foo -      125 +    125 -**_126_** if executing a **_contained command_** and the **_command_** cannot be invoked +  **126** Executing a _contained command_ and the _command_ cannot be invoked      $ podman run busybox /etc; echo $?      Error: container_linux.go:346: starting container process caused "exec: \"/etc\": permission denied": OCI runtime error -      126 +    126 -**_127_** if executing a **_contained command_** and the **_command_** cannot be found +  **127** Executing a _contained command_ and the _command_ cannot be found      $ podman run busybox foo; echo $?      Error: container_linux.go:346: starting container process caused "exec: \"foo\": executable file not found in $PATH": OCI runtime error -      127 +    127 -**_Exit code_** of **_contained command_** otherwise +  **Exit code** _contained command_ exit code -    $ podman run busybox /bin/sh -c 'exit 3' -    # 3 +    $ podman run busybox /bin/sh -c 'exit 3'; echo $? +    3  ## COMMANDS diff --git a/docs/source/markdown/podman-rm.1.md b/docs/source/markdown/podman-rm.1.md index 753b2ee1c..cddf06e3e 100644 --- a/docs/source/markdown/podman-rm.1.md +++ b/docs/source/markdown/podman-rm.1.md @@ -87,10 +87,13 @@ $ podman rm -f --latest  ```  ## Exit Status -**_0_** if all specified containers removed -**_1_** if one of the specified containers did not exist, and no other failures -**_2_** if one of the specified containers is paused or running -**_125_** if the command fails for a reason other than container did not exist or is paused/running +  **0**   All specified containers removed + +  **1**   One of the specified containers did not exist, and no other failures + +  **2**   One of the specified containers is paused or running + +  **125** The command fails for a reason other than container did not exist or is paused/running  ## SEE ALSO  podman(1), podman-image-rm(1) diff --git a/docs/source/markdown/podman-rmi.1.md b/docs/source/markdown/podman-rmi.1.md index f4d946617..78ef2b157 100644 --- a/docs/source/markdown/podman-rmi.1.md +++ b/docs/source/markdown/podman-rmi.1.md @@ -41,10 +41,13 @@ Remove all images and containers.  $ podman rmi -a -f  ```  ## Exit Status -**_0_** if all specified images removed -**_1_** if one of the specified images did not exist, and no other failures -**_2_** if one of the specified images has child images or is being used by a container -**_125_** if the command fails for a reason other than an image did not exist or is in use +  **0**   All specified images removed + +  **1**   One of the specified images did not exist, and no other failures + +  **2**   One of the specified images has child images or is being used by a container + +  **125** The command fails for a reason other than an image did not exist or is in use  ## SEE ALSO  podman(1) diff --git a/docs/source/markdown/podman-run.1.md b/docs/source/markdown/podman-run.1.md index 512a382a6..bf79ea031 100644 --- a/docs/source/markdown/podman-run.1.md +++ b/docs/source/markdown/podman-run.1.md @@ -1022,25 +1022,25 @@ The exit code from `podman run` gives information about why the container  failed to run or why it exited.  When `podman run` exits with a non-zero code,  the exit codes follow the `chroot` standard, see below: -**_125_** if the error is with Podman **_itself_** +  **125** The error is with Podman itself      $ podman run --foo busybox; echo $?      Error: unknown flag: --foo      125 -**_126_** if the **_contained command_** cannot be invoked +  **126** The _contained command_ cannot be invoked      $ podman run busybox /etc; echo $?      Error: container_linux.go:346: starting container process caused "exec: \"/etc\": permission denied": OCI runtime error      126 -**_127_** if the **_contained command_** cannot be found +  **127** The _contained command_ cannot be found      $ podman run busybox foo; echo $?      Error: container_linux.go:346: starting container process caused "exec: \"foo\": executable file not found in $PATH": OCI runtime error      127 -**_Exit code_** of **_contained command_** otherwise +  **Exit code** _contained command_ exit code      $ podman run busybox /bin/sh -c 'exit 3'      3 diff --git a/docs/source/markdown/podman-stop.1.md b/docs/source/markdown/podman-stop.1.md index 3b5f17057..7dbf18887 100644 --- a/docs/source/markdown/podman-stop.1.md +++ b/docs/source/markdown/podman-stop.1.md @@ -38,27 +38,27 @@ to run containers such as CRI-O, the last started container could be from either  The latest option is not supported on the remote client. -**--timeout**, **--time**, **t**=*time* +**--timeout**, **--time**, **-t**=*time*  Timeout to wait before forcibly stopping the container -## EXAMPLE +## EXAMPLES -podman stop mywebserver +$ podman stop mywebserver -podman stop 860a4b235279 +$ podman stop 860a4b235279 -podman stop mywebserver 860a4b235279 +$ podman stop mywebserver 860a4b235279 -podman stop --cidfile /home/user/cidfile-1 +$ podman stop --cidfile /home/user/cidfile-1 -podman stop --cidfile /home/user/cidfile-1 --cidfile ./cidfile-2 +$ podman stop --cidfile /home/user/cidfile-1 --cidfile ./cidfile-2 -podman stop --timeout 2 860a4b235279 +$ podman stop --timeout 2 860a4b235279 -podman stop -a +$ podman stop -a -podman stop --latest +$ podman stop --latest  ## SEE ALSO  podman(1), podman-rm(1) diff --git a/docs/source/markdown/podman.1.md b/docs/source/markdown/podman.1.md index 6e0eff045..acb546ddd 100644 --- a/docs/source/markdown/podman.1.md +++ b/docs/source/markdown/podman.1.md @@ -126,27 +126,27 @@ The exit code from `podman` gives information about why the container  failed to run or why it exited.  When `podman` commands exit with a non-zero code,  the exit codes follow the `chroot` standard, see below: -**_125_** if the error is with podman **_itself_** +  **125** The error is with podman **_itself_**      $ podman run --foo busybox; echo $?      Error: unknown flag: --foo -      125 +    125 -**_126_** if executing a **_contained command_** and the **_command_** cannot be invoked +  **126** Executing a _contained command_ and the _command_ cannot be invoked      $ podman run busybox /etc; echo $?      Error: container_linux.go:346: starting container process caused "exec: \"/etc\": permission denied": OCI runtime error -      126 +    126 -**_127_** if executing a **_contained command_** and the **_command_** cannot be found +  **127** Executing a _contained command_ and the _command_ cannot be found      $ podman run busybox foo; echo $?      Error: container_linux.go:346: starting container process caused "exec: \"foo\": executable file not found in $PATH": OCI runtime error -      127 +    127 -**_Exit code_** of **_contained command_** otherwise +  **Exit code** _contained command_ exit code -    $ podman run busybox /bin/sh -c 'exit 3' -    # 3 +    $ podman run busybox /bin/sh -c 'exit 3'; echo $? +    3  ## COMMANDS | 
