none driver: remove internal calls to "sudo"

Steps to reproduce the issue:

1.installed docker ee v19.03.14. docker instance is up and running 2. installed minikube v1.2.0 as root. 3.Now trying to start minikube cluster (minikube start --vm-driver=none)

Full output of failed command:

Full output of minikube start command used, if not already included: [root@myhostname ~]# minikube start --vm-driver=none

• minikube v1.17.1 on Redhat 7.9
• Using the none driver based on existing profile
• Starting control plane node minikube in cluster minikube
• Restarting existing none bare metal machine for "minikube" ...
• OS release is Red Hat Enterprise Linux Server 7.9 (Maipo)
• Found network options:
  • NO_PROXY=my no_proxy url
  • http_proxy=my http_proxy url
  • https_proxy=my https_proxy url ! This bare metal machine is having trouble accessing https://k8s.gcr.io
• To pull new external images, you may need to configure a proxy: https://minikube.sigs.k8s.io/docs/reference/networking/proxy/
• Preparing Kubernetes v1.20.2 on Docker 19.03.14 ...
  • env NO_PROXY=my no_proxy url
  • env HTTP_PROXY=my http_proxy url
  • env HTTPS_PROXY=my https_proxy url

X Exiting due to GUEST_CERT: certificate symlinks: create symlink for /usr/share/ca-certificates/minikubeCA.pem: sudo /bin/bash -c "test -s /usr/share/ca-certificates/minikubeCA.pem && ln -fs /usr/share/ca-certificates/minikubeCA.pem /etc/ssl/certs/minikubeCA.pem": exit status 126 stdout:

stderr: /bin/bash: /bin/ln: Permission denied

• If the above advice does not help, please let us know:
  • https://github.com/kubernetes/minikube/issues/new/choose

Optional: Full output of minikube logs command: [root@myhostname /]# minikube logs

• The control plane node must be running for this command
  • To start a cluster, run: "minikube start"

could you please let me know how to fix this issue. I just have started learning kubernetes and not an expert in this area.