From 5d9647a12094c953436b1f9af44f88e53db4af16 Mon Sep 17 00:00:00 2001 From: Valentin Rothberg Date: Mon, 23 Nov 2020 10:35:52 +0100 Subject: clarify ps(1) fallback of `podman top` Podman top falls back to executing ps(1) inside the container in the presence of ps-specific flags. Clarify that a bit more to help users resolve issues when, for instance, ps(1) isn't installed in the container. Signed-off-by: Valentin Rothberg --- cmd/podman/containers/top.go | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) (limited to 'cmd') diff --git a/cmd/podman/containers/top.go b/cmd/podman/containers/top.go index 3eb6d2af2..f00b1dce1 100644 --- a/cmd/podman/containers/top.go +++ b/cmd/podman/containers/top.go @@ -18,12 +18,10 @@ import ( ) var ( - topDescription = `Similar to system "top" command. - - Specify format descriptors to alter the output. - - Running "podman top -l pid pcpu seccomp" will print the process ID, the CPU percentage and the seccomp mode of each process of the latest container.` + topDescription = `Display the running processes of a container. + The top command extends the ps(1) compatible AIX descriptors with container-specific ones as shown below. In the presence of ps(1) specific flags (e.g, -eo), Podman will execute ps(1) inside the container. +` topOptions = entities.TopOptions{} topCommand = &cobra.Command{ -- cgit v1.2.3-54-g00ecf