summaryrefslogtreecommitdiff
path: root/libpod
diff options
context:
space:
mode:
authorValentin Rothberg <rothberg@redhat.com>2019-10-10 15:32:14 +0200
committerValentin Rothberg <rothberg@redhat.com>2019-10-14 13:46:10 +0200
commit2d2646883f0b55198eb7f17108a10bbbb5e5c0da (patch)
tree3e8b1c3dd4d1d2eb5ca184863e11c1e846ab022a /libpod
parenta8993bab7861e2181630a022484d3f55f706a460 (diff)
downloadpodman-2d2646883f0b55198eb7f17108a10bbbb5e5c0da.tar.gz
podman-2d2646883f0b55198eb7f17108a10bbbb5e5c0da.tar.bz2
podman-2d2646883f0b55198eb7f17108a10bbbb5e5c0da.zip
change error wording when conmon fails without logs
In some cases, conmon can fail without writing logs. Change the wording of the error message from "error reading container (probably exited) json message" to "container create failed (no logs from conmon)" to have a more helpful error message that is more consistent with other errors at that stage of execution. Signed-off-by: Valentin Rothberg <rothberg@redhat.com>
Diffstat (limited to 'libpod')
-rw-r--r--libpod/oci_conmon_linux.go2
1 files changed, 1 insertions, 1 deletions
diff --git a/libpod/oci_conmon_linux.go b/libpod/oci_conmon_linux.go
index f29758a69..3606a9634 100644
--- a/libpod/oci_conmon_linux.go
+++ b/libpod/oci_conmon_linux.go
@@ -1359,7 +1359,7 @@ func readConmonPipeData(pipe *os.File, ociLog string) (int, error) {
}
}
}
- return -1, errors.Wrapf(ss.err, "error reading container (probably exited) json message")
+ return -1, errors.Wrapf(ss.err, "container create failed (no logs from conmon)")
}
logrus.Debugf("Received: %d", ss.si.Data)
if ss.si.Data < 0 {