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.

Sign up for GitHub

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

Jump to bottom

minikube start --driver=none Not working #18891

Open
dharminfadia opened this issue May 15, 2024 · 1 comment
Open

minikube start --driver=none Not working #18891

dharminfadia opened this issue May 15, 2024 · 1 comment
Labels
co/runtime/docker Issues specific to a docker runtime kind/support Categorizes issue or PR as a support question.

Comments

@dharminfadia
Copy link

What Happened?

I have install minikube on centOS 8 and Docker version is 26 I am starting my minikube with command is minikube start --driver=none giving error kindly help me on this

Attach the log file

logs.txt

Operating System

Other

Driver

None
@spowelljr
Copy link
Member

Hi @dharminfadia, I'm seeing the following error in your logs

time="2024-05-15T15:36:51+05:30" level=fatal msg="connect: connect endpoint 'unix:///var/run/cri-dockerd.sock', make sure you are running as root and the endpoint has been started: context deadline exceeded"

Do you have a cri-dockerd.socket and cri-dockerd.service systemd unit files setup? Seems like the socket may not exist?

@spowelljr spowelljr added kind/support Categorizes issue or PR as a support question. co/runtime/docker Issues specific to a docker runtime labels May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
co/runtime/docker Issues specific to a docker runtime kind/support Categorizes issue or PR as a support question.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@spowelljr @dharminfadia