minikube icon indicating copy to clipboard operation
minikube copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes

facing minikube start error on Azure VM

Open atulkamble opened this issue 1 year ago • 6 comments

What Happened?

Installed docker, kubernetes, kubectl, virtualbox, qemu

minikube_error

Attach the log file

E0903 05:55:28.506565 14173 logs.go:281] Failed to list containers for "kube-apiserver": docker: docker ps -a --filter=name=k8s_kube-apiserver --format={{.ID}}: Process exited with status 1 stdout:

stderr: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? E0903 05:55:29.595361 14173 logs.go:281] Failed to list containers for "etcd": docker: docker ps -a --filter=name=k8s_etcd --format={{.ID}}: Process exited with status 1 stdout:

stderr: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? E0903 05:55:31.494728 14173 logs.go:281] Failed to list containers for "coredns": docker: docker ps -a --filter=name=k8s_coredns --format={{.ID}}: Process exited with status 1 stdout:

stderr: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? E0903 05:55:34.123401 14173 logs.go:281] Failed to list containers for "kube-scheduler": docker: docker ps -a --filter=name=k8s_kube-scheduler --format={{.ID}}: Process exited with status 1 stdout:

stderr: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? E0903 05:55:34.892567 14173 logs.go:281] Failed to list containers for "kube-proxy": docker: docker ps -a --filter=name=k8s_kube-proxy --format={{.ID}}: Process exited with status 1 stdout:

stderr: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? E0903 05:55:35.481080 14173 logs.go:281] Failed to list containers for "kube-controller-manager": docker: docker ps -a --filter=name=k8s_kube-controller-manager --format={{.ID}}: Process exited with status 1 stdout:

stderr: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? E0903 05:55:35.973940 14173 logs.go:281] Failed to list containers for "kindnet": docker: docker ps -a --filter=name=k8s_kindnet --format={{.ID}}: Process exited with status 1 stdout:

stderr: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? E0903 05:55:42.732009 14173 logs.go:195] command /bin/bash -c "sudo which crictl || echo crictl ps -a || sudo docker ps -a" failed with error: /bin/bash -c "sudo which crictl || echo crictl ps -a || sudo docker ps -a": Process exited with status 1 stdout:

stderr: time="2023-09-03T05:55:41Z" level=fatal msg="listing containers: rpc error: code = Unknown desc = Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?" Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? output: "\n** stderr ** \ntime="2023-09-03T05:55:41Z" level=fatal msg="listing containers: rpc error: code = Unknown desc = Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?"\nCannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?\n\n** /stderr **"

❗ unable to fetch logs for: container status

Operating System

Ubuntu

Driver

QEMU

atulkamble avatar Sep 03 '23 05:09 atulkamble

Hi @atulkamble, so you've installed Ubuntu in a VirtualBox VM and running k8s there?

gsowjanya97 avatar Sep 03 '23 13:09 gsowjanya97

Hello @gsowjanya97, I have launched Azure Virtual Machine, connected through ssh, then installed Virtual box on top of Azure VM then tried minikube over there.

atulkamble avatar Sep 04 '23 00:09 atulkamble

@atulkamble Ok, did you allow HTTPS and HTTP ports along with SSH in the Azure Network Security Group?

gsowjanya97 avatar Sep 05 '23 05:09 gsowjanya97

@gsowjanya97 yes.

atulkamble avatar Sep 05 '23 10:09 atulkamble

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Jan 27 '24 16:01 k8s-triage-robot

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:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot avatar Feb 26 '24 17:02 k8s-triage-robot

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:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Reopen this issue with /reopen
  • Mark this issue as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-triage-robot avatar Mar 27 '24 18:03 k8s-triage-robot

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

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:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Reopen this issue with /reopen
  • Mark this issue as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

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.

k8s-ci-robot avatar Mar 27 '24 18:03 k8s-ci-robot