docker-machine create --driver digitalocean --digitalocean-access-token=$DOTOKEN \
--digitalocean-region=sgp1 \
--digitalocean-image=coreos-alpha \
--digitalocean-ssh-key-fingerprint=$DOSSHFINGERPRINT \
--digitalocean-ssh-user=core \
--digitalocean-ssh-key-path=$DOSSHKEYPATH \
node$n
command : sudo systemctl -f start docker
err : exit status 5
output : Failed to start docker.service: Unit early-docker.target not found.
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
exit status 1
I have same error with CoreOS running in VirtualBox:
$ docker-machine create --driver generic --generic-ip-address 192.168.56.106 --generic-ssh-user core coreos01
Running pre-create checks...
Creating machine...
(coreos01) No SSH key specified. Assuming an existing key at the default location.
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 coreOS...
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: ssh command error:
command : sudo systemctl -f start docker
err : exit status 5
output : Failed to start docker.service: Unit early-docker.target not found.
The problem mays come from: https://github.com/docker/machine/blob/master/libmachine/provision/coreos.go#L80-L81
I wonder if https://github.com/docker/machine/pull/3392#issuecomment-274216560 might fix it
CoreOs stable just got the upgrade to 1298.5.0, making this issue affect a lot more people.
Please try 0.10.0 -- there were some systemd (and docker daemon
=> dockerd
) related fixes I think should close this. Thanks !
(I successfully created a coreos-stable
droplet with 0.10.0 btw)
I'm trying to create some machines with coreos-alpha
, for docker stack ...
testing purposes and keep getting this same error.
Most helpful comment
CoreOs stable just got the upgrade to 1298.5.0, making this issue affect a lot more people.