-
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
minikuber start issue #14681
Comments
For CentOS, it needs to be installed in You may find it easier to install the |
Wonder why this is still an issue ? Should have been fixed. |
Problem was with the new code, not noticed since CentOS is not tested. |
Workarounds meanwhile are to move the Or use a supported operating system, like Ubuntu LTS. |
1.Install docker |
Hi @MohSulta, did you have a chance to install
https://kubernetes.io/docs/tasks/debug/debug-cluster/crictl/#installing-crictl /triage needs-information |
Hi @MohSulta – is this issue still occurring? Are additional details available? If so, please feel free to re-open the issue by commenting with Additional information that may be helpful:
Thank you for sharing your experience! |
This issue happened we I was use centos Linux , I delete it and I have
installed Ubuntu then I install minikube and I did face the issue again
…On Wed, 5 Oct 2022, 8:04 pm klaases, ***@***.***> wrote:
Hi @MohSulta <https://github.com/MohSulta> – is this issue still
occurring? Are additional details available? If so, please feel free to
re-open the issue by commenting with /reopen. This issue will be closed
as additional information was unavailable and some time has passed.
Additional information that may be helpful:
-
Whether the issue occurs with the latest minikube release
-
The exact minikube start command line used
-
Attach the full output of minikube logs, run minikube logs
--file=logs.txt to create a log file
Thank you for sharing your experience!
—
Reply to this email directly, view it on GitHub
<#14681 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASSQOLBL3RW73GJQJE6GGRLWBW7LTANCNFSM55DIS3DQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
What Happened?
when i tried to start minikube i faced error that:
minikube start
X Requested memory allocation (1838MB) is less than the recommended minimum 1900MB. Deployments may fail.
X Exiting due to RUNTIME_ENABLE: Temporary Error: sudo crictl version: exit status 1
stdout:
stderr:
sudo: crictl: command not found
the issue if i type command without sudo the command run as normal as:crictl version
Version: 0.1.0
RuntimeName: docker
RuntimeVersion: 20.10.17
RuntimeApiVersion: 1.41.0
but if i use sudo crictl version tha command doesn't work , kindly i need support for this issue sine my OS is Centos linux
Attach the log file
[](url
mylogs.txt
)
Operating System
Other
Driver
VMware
The text was updated successfully, but these errors were encountered: