Add Docker 18.06.1 for Debian Stretch

[granular-ryanbonham]

Add Docker 18.06.1 - Debian Stretch..

Docker 17.03 and 17.09 have bugs that can result in pods failing to terminate due to GRPC errors and PLEG errors.. We hit both bugs after the upgrade to kubernetes 1.10.x from 1.9.x.. Upgrading to 18.06.1 in our clusters has resolved these issues, and we have seen no issues. We have been runnning 18.06.1 across 15 clusters with k8s 10.0.6.

See issue, for other reports of this.
#5747

[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://git.k8s.io/community/CLA.md#the-contributor-license-agreement 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.

[granular-ryanbonham]

Recheck CLA

[granular-ryanbonham]

/assign @andrewsykim

[andrewsykim]

/ok-to-test

[chrisz100]

/lgtm

[justinsb]

Thanks @granular-ryanbonham - I'll read up on the underlying issue, but mapping this and allowing people to choose docker 18.06 is a good idea regardless!

/approve
/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chrisz100, granular-ryanbonham, justinsb

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [justinsb]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[loshz]

Sorry to dig up old PRs, but I am regularly experiencing issues across 6 clusters with Docker 17.03.2-ce on Kubernetes v1.10.9 using kope.io/k8s-1.10-debian-jessie-amd64-hvm-ebs-2018-08-17.

How would I go about using the newer version? Is it as simple as upgrading to use Debian Stretch kope.io/k8s-1.10-debian-stretch-amd64-hvm-ebs-2018-08-17?

If someone could point me in the right direction it would be greatly appreciated 😄

[granular-ryanbonham]

You need to modify your cluster yaml ``kops edit cluster``` and set the docker version

spec:
  docker:
    version: 18.06.1

[deploymentking]

@granular-ryanbonham once you have updated the cluster yaml...do you do anything other than kops update cluster name-of-cluster --yes and then kops rolling update --yes. I have tried your solution but I still seem to be stuck on 17.05

[loshz]

Can confirm that this does not upgrade Docker for me either. I'm still stuck on 17.03

kops version: 1.10
k8s version: 1.10.9
ig image: k8s-1.10-debian-stretch-amd64-hvm-ebs-2018-08-17

[loshz]

I just realised this PR was merged AFTER the 1.10 release, so my version of kops obviously doesn't have these changes. Could be the same problem for you @deploymentking?

[cmosetick]

Like @syscll I'm also still stuck with Docker version 17.03.2-ce.

kops version: 1.11
kubernetes version: 1.12.6
image: kope.io/k8s-1.11-debian-stretch-amd64-hvm-ebs-2018-08-17

I even baked my own AMI based on the image above that has docker version 18.06-ce in it, and created a new node instance group with the custom AMI.

When I inspect the new nodes, I still see docker version 17.03.2.

When I manually launch an instance with aws console and use the custom AMI, it has Docker version 18.06-ce.

[shahbhavik01]

Like @syscll I'm also still stuck with Docker version 17.03.2-ce.

kops version: 1.11
kubernetes version: 1.12.6
image: kope.io/k8s-1.11-debian-stretch-amd64-hvm-ebs-2018-08-17

I even baked my own AMI based on the image above that has docker version 18.06-ce in it, and created a new node instance group with the custom AMI.

When I inspect the new nodes, I still see docker version 17.03.2.

When I manually launch an instance with aws console and use the custom AMI, it has Docker version 18.06-ce.

I'm having the same issue described here as well. I have:
kops version: 1.11.1
kubernetes version 1.10.12

I have:

spec:
    docker:
        version: 18.09.3

[loshz]

@cmosetick @shahbhavik01 you need to make sure you are specifying an exact Docker version that is configured in this slice, for example: 18.06.1

You must also ensure the is corresponds with the exact distro you are using, for example: Debian Stretch.