Better error message when podman probe fails#1408
Merged
p12tic merged 1 commit intocontainers:mainfrom Mar 2, 2026
Merged
Conversation
Signed-off-by: marcsello <punkosdmarcell@rocketmail.com>
p12tic
approved these changes
Mar 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This error message left me scratching my head for a while. My intention with this contribution is to help others not who ran into this, figure out the issue quicker.
In my exact situation, I had wrong permissions on the folder in my CWD, and attempted to execute
podman compose pull. The console output was just this:Which is clearly wrong, as this command was invoked by podman itself.
Looking at the code, I realized that the issue is that any error during running
podman versionresults in this error message. Even ifpodman versionitself returns an error (which it does).With this PR the error message becomes this, which is a little more helpful:
I don't think this change is something that can be unit-tested well, but if you disagree let me know!
It also seems like someone else ran into this issue as well: containers/podman#28004
Fixes: #220 (kindof)