scaleway / docker-machine-driver-scaleway

:whale: Scaleway driver for Docker Machine
MIT License
248 stars 34 forks source link

machine creation failure with latest docker (17-07-02) #66

Closed samuelcolvin closed 7 years ago

samuelcolvin commented 7 years ago

creating a machine I'm getting the following error

➤  docker-machine create -d scaleway --scaleway-commercial-type 'C2S' --scaleway-name ${NAME} ${NAME}
Running pre-create checks...
Creating machine...
(foobar) Creating SSH key...
(foobar) Creating server...
(foobar) Starting server...
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: ssh command error:
command : sudo systemctl -f start docker
err     : exit status 1
output  : Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details.

If I login with ssh (which works fine) I get:

root@foobar:~# systemctl status docker.service
● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
  Drop-In: /etc/systemd/system/docker.service.d
           └─10-machine.conf
   Active: inactive (dead) (Result: exit-code) since Sun 2017-07-02 18:02:08 UTC; 52s ago
     Docs: https://docs.docker.com
  Process: 11253 ExecStart=/usr/bin/docker daemon -H tcp://0.0.0.0:2376 -H unix:///var/run/docker.sock --storage-driver aufs --tlsverify --tlscacert /etc/docker/ca
 Main PID: 11253 (code=exited, status=1/FAILURE)

Jul 02 18:02:08 foobar systemd[1]: Failed to start Docker Application Container Engine.
Jul 02 18:02:08 foobar systemd[1]: docker.service: Unit entered failed state.
Jul 02 18:02:08 foobar systemd[1]: docker.service: Failed with result 'exit-code'.
Jul 02 18:02:08 foobar systemd[1]: docker.service: Service hold-off time over, scheduling restart.
Jul 02 18:02:08 foobar systemd[1]: Stopped Docker Application Container Engine.
Jul 02 18:02:08 foobar systemd[1]: docker.service: Start request repeated too quickly.
Jul 02 18:02:08 foobar systemd[1]: Failed to start Docker Application Container Engine.

Tried twice from scratch and got the same error both times.

I created a machine with size C2M a couple of weeks ago and it went fine. Is this a regression or a size issue?

Please respond ASAP.

local version:

 ➤  machine -v
docker-machine version 0.10.0, build 76ed2a6
 ➤  docker version
Docker version 17.05.0-ce, build 89658be
Client:
 Version:      17.05.0-ce
 API version:  1.29
 Go version:   go1.7.5
 Git commit:   89658be
 Built:        Thu May  4 22:27:42 2017
 OS/Arch:      linux/amd64

Server:
 Version:      17.05.0-ce
 API version:  1.29 (minimum version 1.12)
 Go version:   go1.7.5
 Git commit:   89658be
 Built:        Thu May  4 22:27:42 2017
 OS/Arch:      linux/amd64
 Experimental: false

Let me know if you need any more information.

samuelcolvin commented 7 years ago

Seems to be the same as https://forums.docker.com/t/docker-machine-provisioned-aws-instance-can-not-start-docker-engine/34200

fixed for my by

export MACHINE_DOCKER_INSTALL_URL='https://web.archive.org/web/20170623081500/https://get.docker.com'

before creation