xiting due to K8S_INSTALL_FAILED: updating control plane: generating kubeadm cfg: getting cgroup driver: docker info --format : exit status 2 stdout:

[patreka]

Steps to reproduce the issue:

Full output of failed command:

Full output of minikube start command used, if not already included:

Optional: Full output of minikube logs command:

[RA489]

@patreka Do you mind adding some additional details. Here is additional information that would be helpful:

• The exact minikube start command line used

• The full output of the minikube start command, preferably with --alsologtostderr -v=4 for extra logging.

• The full output of minikube logs

• The full output of kubectl get po -A

Thank you for sharing your experience!

[RA489]

/triage needs-information

[ilya-zuyev]

@patreka any update?

[sharifelgamal]

Hey @patreka – hopefully it’s OK if I close this - there wasn’t enough information to make it actionable, and some time has already passed. If you are able to provide additional details, you may reopen it at any point by adding /reopen to your comment.

Here is additional information that may be helpful to us:

• Whether the issue occurs with the latest minikube release

• The exact minikube start command line used

• The full output of the minikube start command, preferably with --alsologtostderr -v=3 for extra logging.

• The full output of minikube logs

Thank you for sharing your experience!

Just based on the issue title, you might want to try the --force-systemd parameter, but without more information there's no way to know for sure.