Tried to install this platform and getting the following errors.

[cloudmunch1]

Attempt 1:

No availability zone specified - using default [a].
Your AWS parameters file already exists, deleting it...
Creating a new AWS variables file...
Running pre-create checks...
Creating machine...
(myadop) Launching instance...
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 ubuntu(systemd)...
Installing Docker...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
Error creating machine: Error running provisioning: Unable to verify the Docker daemon is listening: Maximum number of retries (10) exceeded

Attempt 2:
No availability zone specified - using default [a].
Your AWS parameters file already exists, deleting it...
Creating a new AWS variables file...
Docker machine 'myadop' already exists

      ###    ########   #######  ########  
     ## ##   ##     ## ##     ## ##     ## 
    ##   ##  ##     ## ##     ## ##     ## 
   ##     ## ##     ## ##     ## ########  
   ######### ##     ## ##     ## ##        
   ##     ## ##     ## ##     ## ##        
   ##     ## ########   #######  ##        

• Initialising ADOP
  Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "...:2376": dial tcp ...:2376: getsockopt: connection refused
  You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
  Be advised that this will trigger a Docker daemon restart which will stop running containers.

Sourcing provider-specific environment files...
Sourcing ./conf/provider/env.provider.aws.sh parameters file...
Your secrets file already exists, will not re-create...
Sourcing variables from platform.secrets.sh file...
The version of your secrets file is up to date, moving on...

• Setting up Docker Network
  Network already exists: local_network
• Pulling Docker Images
  Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "...:2376": dial tcp ...:2376: getsockopt: connection refused
  You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
  Be advised that this will trigger a Docker daemon restart which will stop running containers.

Sourcing provider-specific environment files...
Sourcing ./conf/provider/env.provider.aws.sh parameters file...
Your secrets file already exists, will not re-create...
Sourcing variables from platform.secrets.sh file...
The version of your secrets file is up to date, moving on...
Pulling elasticsearch (elasticsearch:2.1.1)...
ERROR: Couldn't connect to Docker daemon - you might need to run docker-machine start default.

Please let me know what may be wrong.

[kramos]

I had the same problem and had to upgrade my docker-machine:
https://github.com/docker/machine/releases/tag/v0.9.0-rc2
Thanks to @chadmott for the tip here:
#172

[cloudmunch1]

Hmm. I started from a fresh server on aws.
The machine was installed by the script. I did not do a local install. how do I change the version of docker-machine it installs? you want me to edit the compose file and try? Wondering why is it differerent for me only.

[dsingh07]

Hi @kramos @cloudmunch1

This is a known issue with the older version of docker-machine, documented here: docker/machine#3917 (comment)

In brief, it's due to the default AMI not being able to pull down a specific deprecated Linux package.

The solution is to upgrade your docker-machine version, or to update quickstart.sh and add a custom AMI ID.

[cloudmunch1]

I am not seeing any AMI to be passed in quickstart.sh. Can you please help with the exact change to be done pls?

Remember, I did not install docker-machine seperately. I just ran quickstart.sh and I would expect the right compatible version of docker-machine to come up right?

[kramos]

Hi @cloudmunch1 sorry for not being clearer. As part of the pre-reqs you will have installed Docker Engine and Docker Machine on the machine from which you are running the quickstart.sh script. Quickstart is running your local docker-machine command line tool here. Hence you need to upgrade your local installation. Instructions are here. Before running the quickstart you can test you have a working docker-machine like this:
$ docker-machine --version
docker-machine.exe version 0.9.0-rc2, build 7b19591

NB. you will need to do this with a brand new virtual machine.

[cloudmunch1]

ah ok. Trying now. I was at docker-machine version 0.8.0, build b85aac1.

[cloudmunch1]

Was able to install - thank you.