machines time out, cannot run docker hello-world

[xavierbaez]

I tried with the

docker-machine init initialize
➜ ```
This machine has been allocated an IP address, but Docker Machine could not
reach it successfully.
SSH for the machine should still work, but connecting to exposed ports, such as
the Docker daemon port (usually :2376), may not work properly.

2. different driver
   docker-machine create --driver generic --generic-ip-address=192.168.24.108 --generic-ssh-user=developer --generic-ssh-key=$HOME/.ssh/id_rsa docker

➜ docker-machine ls
NAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORS
docker generic Timeout

I am running Big Sur

[xavierbaez]

docker-machine-init initialize
Docker machine "docker" does not exist. Use "docker-machine ls" to list machines. Use "docker-machine create" to add a new one.
Docker machine "docker" does not exist. Use "docker-machine ls" to list machines. Use "docker-machine create" to add a new one.
===> Creating docker machine: docker
Running pre-create checks...
Creating machine...
(docker) Copying /Users/xavier/.docker/machine/cache/boot2docker.iso to /Users/xavier/.docker/machine/machines/docker/boot2docker.iso...
(docker) Creating VirtualBox VM...
(docker) Creating SSH key...
(docker) Starting the VM...
(docker) Check network to re-create if needed...
(docker) Waiting for an IP...
Waiting for machine to be running, this may take a few minutes...
Detecting operating system of created instance...
Waiting for SSH to be available...
Detecting the provisioner...
Provisioning with boot2docker...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...

This machine has been allocated an IP address, but Docker Machine could not
reach it successfully.

SSH for the machine should still work, but connecting to exposed ports, such as
the Docker daemon port (usually <ip>:2376), may not work properly.

You may need to add the route manually, or use another related workaround.

This could be due to a VPN, proxy, or host file configuration issue.

You also might want to clear any VirtualBox host only interfaces you are not using.
Checking connection to Docker...
Error creating machine: Error checking the host: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.99.126:2376": dial tcp 192.168.99.126:2376: i/o timeout
You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
Be advised that this will trigger a Docker daemon restart which might stop running containers.

[xavierbaez]

docker run hello-world
Waiting while Docker starting...

Default \e[91mThe timeout reached, please verify the vm log for errors: /tmp/docker-virtualbox.log\e[39m
Default \e[91mThe timeout reached, please verify the vm log for errors: /tmp/docker-virtualbox.log\e[39m

[xavierbaez]

tail -n 100 -f /tmp/docker-virtualbox.log 
===> Virtual machine 'docker' already started
[INFO] Configuration:

	- Machine Name: docker 
	- Shared Folder: /Users 
	- Mount Options: noacl,async,nfsvers=3 
	- Force: false 

[INFO] machine presence ... 			OK 
[INFO] machine running ... 			FAIL

The machine 'docker' is not running but 'Timeout'! 
===> Virtual machine 'docker' already started
[INFO] Configuration:

	- Machine Name: docker 
	- Shared Folder: /Users 
	- Mount Options: noacl,async,nfsvers=3 
	- Force: false

[sergeycherepanov]

@xavierbaez do you able to create and start a VM in the VirtualBox manually. For example you can try machine with Debian installer dvd.

[xavierbaez]

yeah VM works fine with Virtualbox.

[bossxdev]

Excuse me, It's me same problem i can start debian vm in virtualbox right but don't start with shell

[sergeycherepanov]

@bossxdev please provide the version of VBox.

Also the output of the neofetch if possible.

[xavierbaez]

Hello @sergeycherepanov
I am running version 6.1.36

/etc/vbox/networks.conf

I think the biggest problem was I got confused and thought the file to allow docker-machine host was /etc/vbox/networks

My bad.