Minikube: Upgrade to Docker 1.13

Created on 13 Jul 2017  路  9Comments  路  Source: kubernetes/minikube

It would be awesome to use --cache-from with our 1+ GB PHP images.

As far as the k8s changelog goes, I see that 1.7 supports it.

Would I just need to make a PR like https://github.com/kubernetes/minikube/pull/1658 ?

kinfeature lifecyclstale

Most helpful comment

Update: Docker 1.13 and 17.03.2 have been "officially validated" for use with Kubernetes 1.8 in https://github.com/kubernetes/kubernetes/issues/42926

Changelog is being prepared in https://github.com/kubernetes/features/pull/408

All 9 comments

Could you link to the kubernetes changelog? I see here: https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG.md#external-dependency-version-information

Which doesn't say that 1.13 is supported. The tracking bug is still open afaict: https://github.com/kubernetes/kubernetes/issues/42926

see https://github.com/kubernetes/minikube/pull/1542#issuecomment-318683859

If you are stuck with this, you can preview the custom ISO with:

$ minikube start --iso-url=https://storage.googleapis.com/minikube-builds/1542/minikube-testing.iso

Works perfectly for me! 馃嵒

Yeah, whoops, went down a rabbit hole and found those too, but never commented here. Nothing in the changelog and no progress on that issue. Hopefully 1.8 will support a couple newer versions.

Update: Docker 1.13 and 17.03.2 have been "officially validated" for use with Kubernetes 1.8 in https://github.com/kubernetes/kubernetes/issues/42926

Changelog is being prepared in https://github.com/kubernetes/features/pull/408

YAS!

FWIW, I wrote a short post about how to add an alternative docker client to connect to an older docker engine, like the one running in minikube at the moment.

Linux - Installing alternative versions of docker client

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

This is fixed in the latest release

Was this page helpful?
0 / 5 - 0 ratings