Skip to content
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

Upgrade Docker, from 17.12.1-ce to 18.06.1-ce #3223

Merged
merged 1 commit into from
Oct 17, 2018

Conversation

AkihiroSuda
Copy link
Member

Docker >= 18.06 is needed for securityContext.procMount (Kubernetes >= 1.12)

See kubernetes/kubernetes#64283 and docker-archive/docker-ce@67fe100

Signed-off-by: Akihiro Suda suda.akihiro@lab.ntt.co.jp

Docker >= 18.06 is needed for securityContext.procMount (Kubernetes >= 1.12)

See kubernetes/kubernetes#64283 and docker-archive/docker-ce@67fe100

Signed-off-by: Akihiro Suda <suda.akihiro@lab.ntt.co.jp>
@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Oct 5, 2018
@minikube-bot
Copy link
Collaborator

Can one of the admins verify this patch?

@afbjorklund
Copy link
Collaborator

Wow, even kubeadm have updated their instructions (for docker, as a container runtime alternative):

On each of your machines, install Docker. Version 18.06 is recommended, but 1.11, 1.12, 1.13 and 17.03 are known to work as well. Keep track of the latest verified Docker version in the Kubernetes release notes.

This replaces the previous text, that was a lot more conservative (and we ignored, for 17.06 - 17.12)

On each of your machines, install Docker. Version v1.12 is recommended, but v1.11, v1.13 and 17.03 are known to work as well. Versions 17.06+ might work, but have not yet been tested and verified by the Kubernetes node team.

kubernetes/kubernetes@97c9fa3

diff --git a/cmd/kubeadm/app/util/system/docker_validator.go b/cmd/kubeadm/app/util/system/docker_validator.go
index d6895fa90d4f1..69b84dc660132 100644
--- a/cmd/kubeadm/app/util/system/docker_validator.go
+++ b/cmd/kubeadm/app/util/system/docker_validator.go
@@ -38,7 +38,7 @@ func (d *DockerValidator) Name() string {
 
 const (
 	dockerConfigPrefix        = "DOCKER_"
-	maxDockerValidatedVersion = "17.03"
+	maxDockerValidatedVersion = "18.06"
 )
 
 // TODO(random-liu): Add more validating items.

LGTM

@afbjorklund
Copy link
Collaborator

Note that the above is true for Kubernetes 1.12, but still might not be for earlier versions...
So we should only do this when fixing the rest of the support for the newer versions (> 1.10)

e.g. #3164

@AkihiroSuda
Copy link
Member Author

Docker for Mac/Win distributes vanilla Kubernetes v1.10.3 along with Docker v18.06.1.
So I suppose it is safe to use Docker v18.06 with Kubernetes v1.10.3?

@afbjorklund
Copy link
Collaborator

Supposedly, although someone wanted v1.10.5 (#3074) - so might as well go for v1.10.8 (#3132) ?

Most likely the new Docker would also work with older Kubernetes, but it is untested/unsupported...

@AkihiroSuda
Copy link
Member Author

Is there way to override Docker version as in minikube start --kubernetes-version?

@afbjorklund
Copy link
Collaborator

Unfortunately no, it is baked into the ISO... However, you could download one and overwrite it ?

https://download.docker.com/linux/static/stable/x86_64/

@tstromberg
Copy link
Contributor

/approve

@minikube-bot OK to test

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: AkihiroSuda, tstromberg

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:

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

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 6, 2018
@tstromberg
Copy link
Contributor

The OSX-Virtualbox failure appears to be #3203

I'm not sure about the OSX-Hyperkit failure: it may be the same issue, a new flake, or a new persistent error.

The PR looks good, but I want to get to the bottom of the test failure before approving it.

@AkihiroSuda
Copy link
Member Author

/test OSX-Hyperkit
/test OSX-Virtualbox

@AkihiroSuda
Copy link
Member Author

I can't restart the test, probably because I'm not a maintainer..

@AkihiroSuda
Copy link
Member Author

@tstromberg could you restart the failing tests?

@tstromberg tstromberg merged commit e77d95a into kubernetes:master Oct 17, 2018
@AkihiroSuda
Copy link
Member Author

Thanks for merging, any ETA of v0.31 with this commit?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants