Document minikube docker driver version requirements

[afbjorklund]

Kubernetes itself supports ancient versions, but KIC doesn't really...

kubeadm says:

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

Should verify the Docker version, like we do with the Podman version ?

And have a similar recommendation for minikube, on the driver page.

---

EDIT: I don't think we want to keep supporting 17.03 - 18.09 - or even earlier.

17.03.0-ce
2017-03-01
This release includes bugfixes for 1.13.1 but there are no major feature additions and the API version stays the same.
Upgrading from Docker 1.13.1 to 17.03.0 is expected to be simple and low-risk.

19.03.1
2019-07-25
Security
Fixed loading of nsswitch based config inside chroot under Glibc. CVE-2019-14271

So the easiest would be to require Docker Engine 19.03+ or Docker Desktop 2.1+ ?

Docker Desktop Community 2.1.0.1
2019-08-08
Upgrades
Docker 19.03.1
Kubernetes 1.14.3

Otherwise we need to look at version and API, and implement workarounds.

[medyagh]

machines, install Docker. Version 19.03.11 is recommended, but 1.13.1, 17.03, 17.06, 17.09, 18.06 and 18.09 are known to work as well. Keep track of the latest verified Docker version in the Kuber

Docker has been less problem in version, plus this seems to be more related to the docker inside minikube rather than the outside docker verison.

we could add a link to the kubeadm from our docs, with the version

[afbjorklund]

Docker has been less problem in version, plus this seems to be more related to the docker inside minikube rather than the outside docker verison.

I should have been more specific, what I meant was that we need (want?) to be more strict with the versions used for the Docker driver.

The reason for this ticket was the cp command missing in earlier versions like 17.03: #9075. So the easiest would be to require Docker 19.03 ?

[fejta-bot]

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.

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

[afbjorklund]

We need to check against outdated minor Docker versions, at least.

It should be OK with 18.09 and 19.03 - as long as they are updated...

• https://docs.docker.com/engine/release-notes/18.09/

• https://docs.docker.com/engine/release-notes/19.03/

[afbjorklund]

/remove-lifecycle stale

[fejta-bot]

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.

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

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten

[sharifelgamal]

I do think this is valuable information, it would be an easy check to make as well.

[medyagh]

i think we should check if the very old docker versions fails or not, we added support for ancient docker versions in a PR that we might not wanna block users anymore but I would be okay with informing the user if their docker is more than 2 years old they might wanna look into upgrading it.