From 910baf433fdbc6ad6d85cfeacb5ccc59b37aa634 Mon Sep 17 00:00:00 2001 From: baude Date: Mon, 5 Feb 2018 09:29:46 -0600 Subject: Deprecate --format for podman top Issue #169 describes a common failure when running podman top where if the commands inside the container container a space in them, podman will panic. This was occuring because we take the output from ps and attempt to format it nicely for output and things like JSON. Given that this cannot be predicted or dealt with programatically, the decision was made to deprecate the format switch and simply output what ps provides us. Migrated top integration tests to ginkgo. Resolves Issue: https://github.com/projectatomic/libpod/issues/169 Signed-off-by: baude Closes: #291 Approved by: rhatdan --- docs/podman-top.1.md | 17 ----------------- 1 file changed, 17 deletions(-) (limited to 'docs') diff --git a/docs/podman-top.1.md b/docs/podman-top.1.md index eed15c584..1fca50bda 100644 --- a/docs/podman-top.1.md +++ b/docs/podman-top.1.md @@ -18,9 +18,6 @@ Display the running process of the container. ps-OPTION can be any of the option **--help, -h** Print usage statement -**--format** - Display the output in an alternate format. The only supported format is **JSON**. - **--latest, -l** Instead of providing the container name or ID, use the last created container. If you use methods other than Podman to run containers such as CRI-O, the last started container could be from either of those methods. @@ -42,20 +39,6 @@ root 4 bash system_u:system_r:container_t:s0:c429,c1016 root 0 vi system_u:system_r:container_t:s0:c429,c1016 # ``` -``` -# podman top --format=json f5a62a71b07b -o %cpu,%mem,command,blocked -[ - { - "CPU": "0.0", - "MEM": "0.0", - "COMMAND": "vi", - "BLOCKED": "0000000000000000", - "START": "", - "TIME": "", - "C": "", - "CAUGHT": "", - ... -``` ## SEE ALSO podman(1), ps(1) -- cgit v1.2.3-54-g00ecf