-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
getting error while triggering the minikube start --vm-driver=none #15639
Comments
[root@ip-172-31-32-247 ~]# minikube logs --file=logs.txt
stderr: stderr: stderr: stderr: stderr: W0113 14:59:16.941618 8442 out.go:239] * [root@ip-172-31-32-247 ~]# |
Did you forget to install cri-tools, perhaps ? |
I have installed it [root@ip-172-31-32-247 ~]# which crictl Jan 13 16:03:24 ip-172-31-32-247.ap-south-1.compute.internal cri-dockerd[3710]: time="2023-01-13T16:03:24Z" level=info msg="Star...0s" |
I don't think that |
Similar to: |
awesome......! it works [root@ip-172-31-32-247 ~]# minikube start --vm-driver=none
! The 'none' driver is designed for experts who need to integrate with an existing VM
! kubectl and minikube configuration will be stored in /root
|
But my control plan is not ready [root@ip-172-31-32-247 ~]# kubectl get nodes |
We did some workaround for EL and the legacy sudoers setup before, but it seems like there is some regression. |
can you help on that how can I overcome the issue ? |
Do you possible to take control of my system |
[ec2-user@ip-172-31-32-247 ~]$ kubectl get nodes |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close not-planned |
@k8s-triage-robot: Closing this issue, marking it as "Not Planned". In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
What Happened?
Hi Team
getting this below error
[root@ip-172-31-32-247 cri-dockerd]# minikube start --vm-driver=none
X Exiting due to RUNTIME_ENABLE: Temporary Error: sudo crictl version: exit status 1
stdout:
stderr:
sudo: crictl: command not found
╭─────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ * If the above advice does not help, please let us know: │
│ https://github.com/kubernetes/minikube/issues/new/choose │
│ │
│ * Please run
minikube logs --file=logs.txt
and attach logs.txt to the GitHub issue. ││ │
╰─────────────────────────────────────────────────────────────────────────────────────────────╯
[root@ip-172-31-32-247 cri-dockerd]#
Attach the log file
[root@ip-172-31-32-247 cri-dockerd]# minikube start --vm-driver=none
X Exiting due to RUNTIME_ENABLE: Temporary Error: sudo crictl version: exit status 1
stdout:
stderr:
sudo: crictl: command not found
╭─────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ * If the above advice does not help, please let us know: │
│ https://github.com/kubernetes/minikube/issues/new/choose │
│ │
│ * Please run
minikube logs --file=logs.txt
and attach logs.txt to the GitHub issue. ││ │
╰─────────────────────────────────────────────────────────────────────────────────────────────╯
[root@ip-172-31-32-247 cri-dockerd]#
Operating System
Other
Driver
None
The text was updated successfully, but these errors were encountered: