Skip to content
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

Closed
MohSulta opened this issue Jul 30, 2022 · 8 comments
Closed

minikuber start issue #14681

MohSulta opened this issue Jul 30, 2022 · 8 comments
Labels
co/none-driver kind/bug Categorizes issue or PR as related to a bug. kind/support Categorizes issue or PR as a support question. os/linux priority/backlog Higher priority than priority/awaiting-more-evidence. triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@MohSulta
Copy link

What Happened?

when i tried to start minikube i faced error that:
minikube start

  • minikube v1.26.0 on Centos 7.9.2009
  • Using the none driver based on existing profile

X Requested memory allocation (1838MB) is less than the recommended minimum 1900MB. Deployments may fail.

  • Starting control plane node minikube in cluster minikube
  • Restarting existing none bare metal machine for "minikube" ...
  • OS release is CentOS Linux 7 (Core)

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

@afbjorklund afbjorklund added co/none-driver kind/support Categorizes issue or PR as a support question. labels Jul 30, 2022
@afbjorklund
Copy link
Collaborator

afbjorklund commented Jul 30, 2022

For CentOS, it needs to be installed in /usr/bin/crictl since root doesn't have /usr/local/bin in PATH.

You may find it easier to install the cri-tools rpm package instead, as provided by kubernetes upstream.

@afbjorklund
Copy link
Collaborator

Wonder why this is still an issue ? Should have been fixed.

@afbjorklund
Copy link
Collaborator

Problem was with the new code, not noticed since CentOS is not tested.

@afbjorklund afbjorklund added kind/bug Categorizes issue or PR as related to a bug. priority/backlog Higher priority than priority/awaiting-more-evidence. os/linux and removed kind/support Categorizes issue or PR as a support question. labels Jul 31, 2022
@afbjorklund
Copy link
Collaborator

Workarounds meanwhile are to move the crictl binary.

Or use a supported operating system, like Ubuntu LTS.

@JesudassJosephraj
Copy link

1.Install docker
2.install kubectl
3.install minikube according to you device compatibility (https://minikube.sigs.k8s.io/docs/start/)
4.once all done before starting minikube install conntrack ( apt install conntrack)
5. After that if you get any error like juju,cric dockered id, cric ctl not found any error it may be..
6. jusz give this command minikube start --force
7. Minikube works without any error following above steps..

@klaases
Copy link
Contributor

klaases commented Sep 10, 2022

Hi @MohSulta, did you have a chance to install crictl?

crictl is a command-line interface for CRI-compatible container runtimes. You can use it to inspect and debug container runtimes and applications on a Kubernetes node. crictl and its source are hosted in the cri-tools repository.

https://kubernetes.io/docs/tasks/debug/debug-cluster/crictl/#installing-crictl

/triage needs-information
/kind support

@k8s-ci-robot k8s-ci-robot added triage/needs-information Indicates an issue needs more information in order to work on it. kind/support Categorizes issue or PR as a support question. labels Sep 10, 2022
@klaases
Copy link
Contributor

klaases commented Oct 5, 2022

Hi @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!

@klaases klaases closed this as completed Oct 5, 2022
@MohSulta
Copy link
Author

MohSulta commented Oct 5, 2022 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
co/none-driver kind/bug Categorizes issue or PR as related to a bug. kind/support Categorizes issue or PR as a support question. os/linux priority/backlog Higher priority than priority/awaiting-more-evidence. triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
None yet
Development

No branches or pull requests

5 participants