refactor: use existing docker ApiClient instance instead of creating a new one #504
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.
Use existing docker ApiClient instance instead of creating a new one.
scheduler tests were failing using docker desktop. see docker/docker-py#3198 and docker/docker-py#3219 for more detail. the gist is docker creates a
context
for docker desktop that uses a separate, non-default unix socket. for docker-py to play nicely with docker desktop, you must setDOCKER_HOST
to the appropriate unix socket. You can locate the appropriate socket addr using:docker context inspect $(docker context show) | awk -F '"' '/"Host"/ {print $4}'
.dmod.scheduler
--0.10.2
Changes