summaryrefslogtreecommitdiff
path: root/cmd/podman/info.go
diff options
context:
space:
mode:
authorbaude <bbaude@redhat.com>2018-02-20 10:57:37 -0600
committerAtomic Bot <atomic-devel@projectatomic.io>2018-02-21 14:22:36 +0000
commit6ce70a33c5825c0f4d2afae7643db95e8b7d46f1 (patch)
tree5d387d97c7cac2a0ca8b9c8a8c0ceed2a8c472ff /cmd/podman/info.go
parente929e7de4cf537c5de5817b7c086bc4883a8b93a (diff)
downloadpodman-6ce70a33c5825c0f4d2afae7643db95e8b7d46f1.tar.gz
podman-6ce70a33c5825c0f4d2afae7643db95e8b7d46f1.tar.bz2
podman-6ce70a33c5825c0f4d2afae7643db95e8b7d46f1.zip
Inspect output should be in array form
Inspect should be able to inspect one or more containers depending on the user input. Therefore, inspect output should be in array format so the consumer could potentially iterate it. This PR allows users to specify one more or containers|images|or a mix for inspection. The output, as stated, is therefore in array form. This holds true even for a singular image. In the case that the user enters an invalid container|image "name", we handle that gracefully. Podman will output json for the valid names until it reaches the invalid one. For example: In this case, podman will out the json for alpine and then print an error about 123 being invalid. It will not continute onto busybox. This behavior imatates docker. This addresses issue #360 Signed-off-by: baude <bbaude@redhat.com> Closes: #371 Approved by: baude
Diffstat (limited to 'cmd/podman/info.go')
0 files changed, 0 insertions, 0 deletions