Exit with error when Docker version is too old

[dinever]

#10369 dropped the error in the Docker version validation to support old Docker versions.

With this change, the users get a confusing docker info --format : exit status 2 error when they're using ancient Docker versions (<1.13.0) that don't even support docker info --version, see
#11480
#11538

Should we exit with an error and tell users to upgrade their Docker version when it's way too old?

One option is to define two constants: minDockerVer (e.g. 1.13.0) and recommendedDockerVer (18.09.0):

1. If user Docker version < minDockerVer: Exit with error message
2. If user Docker version < recommendedDockerVer: Only show suggestions to upgrade Docker
3. If user Docker version >= recommendedDockerVer: Do nothing

[dinever]

Related to #9077

docker info --format and docker system were both added in v1.13.0

docker cp -a was added in v18.06.0: docker/cli@7a767a1

[dinever]

Another option is to remind the user to upgrade Docker when commands like docker info --format and docker system failed.

[RA489]

/kind support

[afbjorklund]

We should bump the required version for the Docker driver to 2018, and leave the old versions only for the container runtime...

We don't want to spend all resources "supporting" old deprecated versions of Docker and Podman, when even upstream doesn't.

[afbjorklund]

@dinever : we already have var minDockerVersion = []int{18, 9, 0} since 4500be1

It should exit with an error, at least require some kind of force flag to run. Recommend 20.10.

[medyagh]

I am in favor of at least giving solution message to user if their old docker is cause of the problem like this #11480

(we should still allow users to run old dockers with --force if they wanna do it anyways)

@dinever I would accept a PR that does that (or updates our current validation)

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[sharifelgamal]

Let's add this back in soon.

[medyagh]

@dinever are u interested in this PR ?