aboutsummaryrefslogtreecommitdiff
path: root/libpod/runtime_ctr_freebsd.go
diff options
context:
space:
mode:
authorPaul Holzinger <pholzing@redhat.com>2022-09-07 15:32:50 +0200
committerPaul Holzinger <pholzing@redhat.com>2022-09-13 10:33:14 +0200
commit43f7bdf8229ee04ab17fcf53cf302c5d98d11f8e (patch)
tree2b4558ab7c7bb9777c559c01558cf7ca31f431c3 /libpod/runtime_ctr_freebsd.go
parent00240a0e2e1f031926fd7f21d9ef5b0d27335e47 (diff)
downloadpodman-43f7bdf8229ee04ab17fcf53cf302c5d98d11f8e.tar.gz
podman-43f7bdf8229ee04ab17fcf53cf302c5d98d11f8e.tar.bz2
podman-43f7bdf8229ee04ab17fcf53cf302c5d98d11f8e.zip
podman inspect return exit code > 0 on print error
Unlikely to happen but when there is an error printing the data to stdout (either as json or go template) we should not just log it and exit with 0. Instead return a proper error and exit with 125. Signed-off-by: Paul Holzinger <pholzing@redhat.com>
Diffstat (limited to 'libpod/runtime_ctr_freebsd.go')
0 files changed, 0 insertions, 0 deletions