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
Don't use docker.Client instance from context if missing attributes #39973
Conversation
@terminalmage, thanks for your PR! By analyzing the history of the files in this pull request, we identified @ticosax, @rallytime and @tyhunt99 to be potential reviewers. |
Hold off on merging this, the issue might be something with docker-py itself. |
Under some circumstances (which I can't reliably reproduce), the docker.Client() instance does not have a timeout attribute, causing anything that needs to use the docker client to result in a traceback. This fixes this corner case (later branches initialize the timeout differently).
ad24ff8
to
869416e
Compare
OK I changed the approach on this PR and renamed it. For some reason, on one of @SaltyCharles' test boxes, the client instance when returned from the |
@terminalmage Can you give some instructions so I can reproduce this behavior myself ? |
@ticosax Sorry, but I can't. I only ever reproduced this on one of @SaltyCharles' VMs, which he gave me access to use. I tried to reproduce on my laptop, and on a couple Vagrant boxes with Docker installed on them, and I never was able to reproduce. The PR should be pretty straightforward though. |
It might be a bigger issue than docker-py itself, or just an edge case related to local setup of packages. |
Add comment explaining change from #39973
Under some circumstances (which I can't reliably reproduce), the
docker.Client() instance does not have a timeout attribute, causing
anything that needs to use the docker client to result in a traceback.
This fixes this corner case (later branches initialize the timeout
differently).