virtualbox: Error dialing TCP: dial tcp 127.0.0.1:x: connect: connection refused #7674
Labels
kind/support
Categorizes issue or PR as a support question.
needs-solution-message
Issues where where offering a solution for an error would be helpful
triage/needs-information
Indicates an issue needs more information in order to work on it.
Comments
|
π minikube v1.9.2 on Ubuntu 16.04 β [CREATE_TIMEOUT] Failed to start virtualbox VM. "minikube start" may fix it. creating host: create host timed out in 120.000000 seconds |
|
Output of minikube start --alsologtostderr -v=8 is as below |
priyawadhwa
added
the
kind/support
tstromberg
changed the title
|
Just curious: It's unlikely, but does Basically, the VM appears to come up, but the port-forward to SSH doesn't seem to work. |
tstromberg
added
the
triage/needs-information
|
Nope. Still the same issue |
tstromberg
changed the title
|
Thank you! Are you running minikube from inside of a VM? I ask because VirtualBox can have strange networking problems in a nested VM environment. If you are running minikube within a VM, I strongly recommend using If this is a physical machine running VirtualBox, upgrade to the latest VirtualBox 6.1.6, and if it has issues, please run the following commands: Confirm that the VM boots up and results in a screen that shows a login prompt that says:
If things look correct, please share the output of the following command:
I'm specifically looking for a NIC rule like: Using the host port mentioned here, please share the output of: I look forward to your reply, as I would like to update this error message to point to this conversation once we've come to a solution. |
|
Yes am running a ubuntu VM and trying to run minikube from inside the ubuntu VM. |
|
@jyobeer - Yes. Install Docker inside the VM: https://docs.docker.com/engine/install/ubuntu/ For more information about the Docker driver, see: https://minikube.sigs.k8s.io/docs/drivers/docker/ |
tstromberg
added
the
needs-solution-message
|
I installed docker and then tried minikube start --driver=docker but it still fails - dmadmin@ubuntu:~$ minikube start --driver=docker β 'docker' driver reported an issue: exit status 1 π Starting control plane node m01 in cluster minikube π£ Failed to start docker container. "minikube start" may fix it.: recreate: creating host: create: creating: create kic node: creating volume for minikube container: output Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post http://%2Fvar%2Frun%2Fdocker.sock/v1.40/volumes/create: dial unix /var/run/docker.sock: connect: permission denied πΏ minikube is exiting due to an error. If the above message is not useful, open an issue: |
|
@jyobeer here is the link to docker site how to add user to docker group |
medyagh
added
the
priority/important-longterm
|
we could add a message in minikube if we detect this to direct user to add user permission |
|
added the user to the group but still receiving the same error. Any other pointers please? |
|
@jyobeer - Can you share the output of:
I personally suspect that running logging out or running |
tstromberg
removed
the
priority/important-longterm
|
@tstromberg please find below the output -
|
|
Hey @jyobeer that output looks correct to me. Can you run If you need sudo, you could try following the docker instructions for running as a non-root user: https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user |
|
Hey @jyobeer any update here? |
|
Hey @jyobeer -- hopefully it's OK if I close this - there wasn't enough information to make it actionable, and some time has already passed. If you are able to provide additional details, you may reopen it at any point by adding /reopen to your comment. Thank you for sharing your experience! |
|
Still the same issue. groups sheng root adm cdrom sudo dip plugdev lpadmin lxd sambashare mysql microk8s dockerstat /var/run/docker.sock File: /var/run/docker.sock
Size: 0 Blocks: 0 IO Block: 4096 socket
Device: 19h/25d Inode: 1614 Links: 1
Access: (0660/srw-rw----) Uid: ( 0/ root) Gid: ( 998/ docker)
Access: 2022-03-08 12:31:53.034622311 +0800
Modify: 2022-03-08 12:30:32.418308361 +0800
Change: 2022-03-08 12:30:32.418308361 +0800
docker run hello-world docker run hello-world at ο 13:54:16
Unable to find image 'hello-world:latest' locally
latest: Pulling from library/hello-world
2db29710123e: Pull complete
Digest: sha256:97a379f4f88575512824f3b352bc03cd75e239179eea0fecc38e597b2209f49a
Status: Downloaded newer image for hello-world:latest
Hello from Docker!
This message shows that your installation appears to be working correctly.
To generate this message, Docker took the following steps:
1. The Docker client contacted the Docker daemon.
2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
(amd64)
3. The Docker daemon created a new container from that image which runs the
executable that produces the output you are currently reading.
4. The Docker daemon streamed that output to the Docker client, which sent it
to your terminal.
To try something more ambitious, you can run an Ubuntu container with:
$ docker run -it ubuntu bash
Share images, automate workflows, and more with a free Docker ID:
https://hub.docker.com/
For more examples and ideas, visit:
https://docs.docker.com/get-started/error info: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce the issue:
Full output of failed command:
Full output of
minikube startcommand used, if not already included:π minikube v1.9.2 on Ubuntu 16.04
β¨ Using the virtualbox driver based on existing profile
π Starting control plane node m01 in cluster minikube
π Restarting existing virtualbox VM for "minikube" ...
π€¦ StartHost failed, but will try again: driver start: Maximum number of retries (5) exceeded
π Restarting existing virtualbox VM for "minikube" ...
π£ Failed to start virtualbox VM. "minikube start" may fix it.: driver start: Maximum number of retries (5) exceeded
Optional: Full output of
minikube logscommand:The text was updated successfully, but these errors were encountered: