-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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 to Docker 1.13 #1691
Comments
Whoops, solved by #1542 |
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: kubernetes/kubernetes#42926 |
see #1542 (comment)
|
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 kubernetes/kubernetes#42926 Changelog is being prepared in kubernetes/enhancements#408 |
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. |
Issues go stale after 90d of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or |
This is fixed in the latest release |
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 #1658 ?
The text was updated successfully, but these errors were encountered: