Not a Contribution: Docker SDK Image Pull function hides real exception
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.2k
- Forks
- 1.7k
- Avg merge
- 13d 8h
- Merged PRs (30d)
- 2
Description
Not a Contribution!
When receiving an exception like:
3eeaaaaaaa98: Pull complete
failed to register layer: Error processing tar file(exit status 1):
Container ID 120111 cannot be mapped to a host ID
The "nice" Docker SDK function rethrows it as a 404 Image not found. While the docker_client.api.pull exposes the real error in the stream of stdout.
This is extremely incorrect behavior since it hides the real error (in this case, issues around how docker handles extremely high userids)
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
Start by comparing the Docker SDK Image Pull function with docker_client.api.pull, focusing on how the SDK handles errors from the pull stream. Reproduce the shown layer-registration failure if possible and trace where it becomes a 404 Image not found. Done means the underlying pull error is no longer hidden by the SDK exception.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100