Provide a way to read stdout on non-zero exit code
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.2k
- Forks
- 1.7k
- Avg merge
- 13d 8h
- Merged PRs (30d)
- 2
Description
If a container exits non-zero, an ContainerError is thrown, but this object only provides access to stderr, not stdout. Some binaries write their logs/errors to stdout instead of stderr, or at least stdout can provide a clue on why the command failed.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or tests. Start by locating ContainerError and the existing stderr exposure in docker-py, then trace how non-zero container exits are handled. Done means callers can access stdout when a container exits non-zero, with coverage for output written to stdout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100