I have to say that Installing Docker has been a bit of a nightmare. For all of the usability that Docker interfaces provide, the underlying problems of installing Docker on Windows 7 and OS X 10.8 provide a considerable level of frustration. In Windows, errors referring to the system’s ability to run a Virtual Machine emerge while an Intel application tells me that the system is capable of implementing a virtual machine is the beginning of the list of problems. Those as shortly followed by problems associated with the inability to run the hello-world application. There is mention that the NDIS driver is somehow part of the problem, but that is not solved additional trolling through the infosphere, provides information that there are indications that the VM’s are not properly installed. Really ?
In the end I gave up. I will probably go back, but this is such a timewaster. So I thought OS X would be easier…
I try to install the application but am warned part way through that the installation problem I am seeing with a VM are known and the system is going to try to recover. Really, again ?
But I still can’t install Docker on my OS X 10.8.5 platform. On Debian it’s a piece of cake -seconds of command line and we are done.
There are so many problems with this installation related to different versions of the OS that for a novice like myself to try to figure them out is rather difficult.
I actually expected a lot better from Docker, given its shiny look and fast response. Clearly my incompetence is at the root of this set of problems. Or is it ?
Thanks for your suggestion Murad. But I used https://docs.docker.com/toolbox/toolbox_install_mac/ which says that the toolbox should work on 10.8
On Windows 7 after I uninstall docker toolbox, it still leaves a lot of material behind in the .docker (note the period preceding) directory. If I erase this then I can re-install the toolbox. Right now when I start the toolbox I get … "looks like something went wrong in step “Checking status on default”. A search on this term provides a number of suggestions, none of which helps me get to running hello-world
I kind of get the sense that these problems are known and are not resolved. But I would be delighted to find out that I have no idea what I am talking about. Which happens often.
And with OS X 10.8 toolbox has its own problems. Viz:
Begin install messages
--------------------------------------------//---------------------------------------------------------------- Running pre-create checks… (default) Default Boot2Docker ISO is out-of-date, downloading the latest release… (default) Latest release for github.com/boot2docker/boot2docker is v17.03.1-ce (default) Downloading /Users/admin/.docker/machine/cache/boot2docker.iso from https://github.com/boot2docker/boot2docker/releases/download/v17.03.1-ce/boot2docker.iso… (default) 0%…10%…20%…30%…40%…50%…60%…70%…80%…90%…100% Creating machine… (default) Copying /Users/admin/.docker/machine/cache/boot2docker.iso to /Users/admin/.docker/machine/machines/default/boot2docker.iso… (default) Creating VirtualBox VM… (default) Creating SSH key… (default) Starting the VM… (default) Check network to re-create if needed… (default) Creating a new host-only adapter produced an error: /usr/local/bin/VBoxManage hostonlyif create failed: (default) 0%… (default) Progress state: NS_ERROR_FAILURE (default) VBoxManage: error: Failed to create the host-only adapter (default) VBoxManage: error: Failed to execute ‘VBoxNetAdpCtl add’ (exit status: 768) (default) VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface (default) VBoxManage: error: Context: “RTEXITCODE handleCreate(HandlerArg *)” at line 71 of file VBoxManageHostonly.cpp
_(default) _ (default) This is a known VirtualBox bug. Let’s try to recover anyway… Error creating machine: Error in driver during machine creation: Error setting up host only network on machine start: The host-only adapter we just created is not visible. This is a well known VirtualBox bug. You might want to uninstall it and reinstall at least version 5.0.12 that is is supposed to fix this issue Starting “default”… (default) Check network to re-create if needed… (default) Creating a new host-only adapter produced an error: /usr/local/bin/VBoxManage hostonlyif create failed: (default) 0%… (default) Progress state: NS_ERROR_FAILURE (default) VBoxManage: error: Failed to create the host-only adapter (default) VBoxManage: error: Failed to execute ‘VBoxNetAdpCtl add’ (exit status: 768) (default) VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface (default) VBoxManage: error: Context: “RTEXITCODE handleCreate(HandlerArg *)” at line 71 of file VBoxManageHostonly.cpp
_(default) _ (default) This is a known VirtualBox bug. Let’s try to recover anyway… Error setting up host only network on machine start: The host-only adapter we just created is not visible. This is a well known VirtualBox bug. You might want to uninstall it and reinstall at least version 5.0.12 that is is supposed to fix this issue Regenerate TLS machine certs? Warning: this is irreversible. (y/n): Regenerating TLS certificates Waiting for SSH to be available…
----------------------------------------------//--------------------------------------------------------
So some questions: This error message from above says
“Error creating machine: Error in driver during machine creation: Error setting up host only network on machine start: The host-only adapter we just created is not visible. This is a well known VirtualBox bug. You might want to uninstall it and reinstall at least version 5.0.12 that is is supposed to fix this issue”
The script continues timing out at the creation of the SSH keys with Too many retries waiting for SSH to be available. Last error: Maximum number of retries (60) exceeded Error checking TLS connection: Host is not running
Error getting IP address: Host is not running
d_ocker is configured to use the default machine with IP _
_F_or help getting started, check out the docs at https://docs.docker.com
**Well, the VirtualBox installation is V 5.1.14 so what is going on here? It seems like these scripts are pretty much abandoned, or at least not fed much
