Add support for docker 17.09.0 version

[dvavili]

Add support for docker version 17.09.0 version

[k8s-ci-robot]

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://github.com/kubernetes/kubernetes/wiki/CLA-FAQ to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
• If you have done the above and are still having issues with the CLA being reported as unsigned, please email the CNCF helpdesk: helpdesk@rt.linuxfoundation.org

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[chrislovecnm]

Thanks for your PR!

We already include the correct version of docker for Kubernetes 1.8, which version is this for? You are able to set the docker version as well. #sig-node certifies the different docker versions.

/assign @justinsb

[dvavili]

From my understanding, the docker version needs to be part of this list to be set explicitly in the cluster spec. This is my use-case - I'm trying to run P3 instances on AWS with nvidia-docker2 and nvidia-docker:2.0 is dependent on 17.09.0 features. Would be good to have this version supported.

[dvavili]

I also hit a couple of issues with P3 instances because of the driver version. Will raise a PR to address that as well.

[justinsb]

Makes sense - thanks @dvavili . @chrislovecnm is right that we don't want to change the default, but you're right that mapping it doesn't change the default and is required for people to specify that docker version (e.g. if you suspect a problem fixed in a later docker version).

Apparently we should be using device plugins, BTW, but I haven't really looked into this:
kubernetes/kubernetes#54011

/ok-to-test
/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: justinsb

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these OWNERS Files:

• OWNERS [justinsb]

You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

[k8s-github-robot]

/test all [submit-queue is verifying that this PR is safe to merge]

[k8s-github-robot]

Automatic merge from submit-queue.