Add root or sudo requirements for the KIC drivers to the documentation

[afbjorklund]

Currently we just refer to the upstream documentation, but don't mention the extra step needed:

• https://minikube.sigs.k8s.io/docs/drivers/docker/

  and https://docs.docker.com/engine/install/ubuntu/

  $ sudo apt-get install docker-ce docker-ce-cli containerd.io

• https://minikube.sigs.k8s.io/docs/drivers/podman/

  and https://podman.io/getting-started/installation.html

  $ sudo apt-get -qq -y install podman

Then it will fail on the first minikube start instead, mentioning what needed to be done before.

❗  'docker' driver reported an issue: "docker version --format {{.Server.Version}}" exit status 1: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.40/version: dial unix /var/run/docker.sock: connect: permission denied
💡  Suggestion: Add your user to the 'docker' group: 'sudo usermod -aG docker $USER && newgrp docker'
📘  Documentation: https://docs.docker.com/engine/install/linux-postinstall/

❗  'podman' driver reported an issue: "sudo -n podman version --format {{.Version}}" exit status 1: sudo: a password is required
💡  Suggestion: Add your user to the 'sudoers' file: "$USER ALL=(ALL) NOPASSWD: /usr/local/bin/podman"
📘  Documentation: https://podman.io

---

So we might as well add those steps to the documentation, in the first place ?

Note that sudo docker and sudo podman do work fine, but with a password prompt...

We should also take care to mention the security implications of removing the password.

It means that anything can run docker and podman commands - not only minikube.

[afbjorklund]

Technically it is possible to run docker with sudo or to add a podman group, it's just not "standard"

We should also note that these steps only apply when running locally on Linux, not on Mac or Win.

[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

[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-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten