Improve logging in InternalCommandPortListeningCheck (#2984) #3001
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.
Related to:
Mock Server doesn't start after updating to 5.11.0 #2984
When /bin/sh -c $command exists with code 126 (Command invoked cannot execute), the error output is not logged.
An example, /bin/sh is not available starting certain image version:
OCI runtime exec failed: exec failed: container_linux.go:349: starting container process caused "exec: "/bin/sh": stat /bin/sh: no such file or directory": unknown
Such error output could be logged to assist troubleshooting. It shouldn't bloat logs since such outcome is rare.