-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rootless: propagate errors from info #2588
rootless: propagate errors from info #2588
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: giuseppe The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
libpod/runtime.go
Outdated
|
||
if output, err := cmd.CombinedOutput(); err != nil { | ||
if _, ok := err.(*exec.ExitError); !ok { | ||
return errors.Wrapf(err, "Error waiting info while refreshing state: %s", os.Args[0]) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Waiting for info
One nit otherwise LGTM |
I agree with @mheon LGTM, Merge once you fix error message. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM once touched up.
we use "podman info" to reconfigure the runtime after a reboot, but we don't propagate the error message back if something goes wrong. Closes: containers#2584 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
62f963d
to
cc411dd
Compare
/lgtm |
we use "podman info" to reconfigure the runtime after a reboot, but we
don't propagate the error message back if something goes wrong.
Closes: #2584
Signed-off-by: Giuseppe Scrivano gscrivan@redhat.com