Skip to content

Conversation

hannseman
Copy link
Contributor

If volume_driver is passed to containers.create it will crash as it have been moved to HostConfig in the APIClient.

This PR moves volume_driver from RUN_CREATE_KWARGS to RUN_HOST_CONFIG_KWARGS.

Added a test to verify the fix.

Fixes #2271

Fixes docker#2271

Signed-off-by: Hannes Ljungberg <hannes@5monkeys.se>
Copy link
Contributor

@shin- shin- left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Looks like the CI failures are flakes. LGTM!

@shin- shin- added this to the 4.0.0 milestone Mar 23, 2019
@hannseman
Copy link
Contributor Author

Yes I saw that failure of test_attach_stream_and_cancel in #2287 as well. Is there an easy way to trigger a rerun of the jenkins build? I tried closing/opening the PR but that only triggered the other checks.

@ijc
Copy link
Contributor

ijc commented Mar 25, 2019

I kicked Jenkins.

@ijc
Copy link
Contributor

ijc commented Mar 25, 2019

And it's green on repeat, I will merge based on @shin-'s earlier LGTM. Thanks @hannseman

I raised #2291 for the flakey test which this hit the first time..

@ijc ijc merged commit c1fea8e into docker:master Mar 25, 2019
@hannseman
Copy link
Contributor Author

@ijc thanks! I haven't been able to reproduce the test_attach_stream_and_cancel failure locally.

@shin- thanks for the review!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

volume_driver isn't recognized as a host config keyword argument when using DockerClient API

3 participants