Docker-machine provisionnés exemple SSFE ne peut pas démarrer le moteur docker

Question

Quand je commence une instance EC2 avec

docker-machine create --driver amazonec2 --amazonec2-region eu-central-1 --amazonec2-instance-type t2.2xlarge aws-test 

docker machine peut créer la machine virtuelle, échanger les certs mais le démarrage du moteur tombe en panne.

Connexion du EC2:

ubuntu@aws-manager2:~$ systemctl status docker.service 
 
● docker.service - Docker Application Container Engine 
 
    Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: e 
 
    Drop-In: /etc/systemd/system/docker.service.d 
 
      └─10-machine.conf 
 
    Active: inactive (dead) (Result: exit-code) since Thu 2017-06-29 09:18:44 UTC 
 
    Docs: https://docs.docker.com 
 
    Process: 5263 ExecStart=/usr/bin/docker daemon -H tcp://0.0.0.0:2376 -H unix:/ 
 
Main PID: 5263 (code=exited, status=1/FAILURE) 
 

 
Jun 29 09:18:44 aws-manager2 systemd[1]: Failed to start Docker Application Cont 
 
Jun 29 09:18:44 aws-manager2 systemd[1]: docker.service: Unit entered failed sta 
 
Jun 29 09:18:44 aws-manager2 systemd[1]: docker.service: Failed with result 'exi 
 
Jun 29 09:18:44 aws-manager2 systemd[1]: docker.service: Service hold-off time o 
 
Jun 29 09:18:44 aws-manager2 systemd[1]: Stopped Docker Application Container En 
 
Jun 29 09:18:44 aws-manager2 systemd[1]: docker.service: Start request repeated 
 
Jun 29 09:18:44 aws-manager2 systemd[1]: Failed to start Docker Application Cont 
 
lines 1-16/16 (END)...skipping... 
 
● 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 Thu 2017-06-29 09:18:44 UTC; 1min 53s ago 
 
    Docs: https://docs.docker.com 
 
    Process: 5263 ExecStart=/usr/bin/docker daemon -H tcp://0.0.0.0:2376 -H unix:///var/run/docker.sock --s 
 
Main PID: 5263 (code=exited, status=1/FAILURE) 
 

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

Connexion au démarrage:

$ docker-machine create --driver amazonec2 --amazonec2-region eu-central-1 --amazonec2-instance-type t2.2xlarge aws-manager2 
 
Running pre-create checks... 
 
Creating machine... 
 
(aws-manager2) 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: 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.

Hier, il a travaillé avec le même configuratio n. Pourrait-il y avoir un changement dans l'AIM utilisé depuis hier? Je l'ai essayé depuis un autre hôte mais j'ai aussi la même erreur.

Answer 1

Je vais avoir le même problème avec la commande suivante:

docker-machine create --driver amazonec2 --amazonec2-region us-east-2 --amazonec2-zone c --amazonec2-ami ami-618fab04 --amazonec2-instance-type m4.large --amazonec2-vpc-id vpc-97cf5ffe --amazonec2-iam-instance-profile S3RW searchtest 

Et la même commande fonctionnait aussi parfaitement hier. Lorsque je me connecte à l'instance EC2 et essayez de démarrer manuellement docker, je reçois l'erreur suivante:

Jun 29 16:10:41 searchtest systemd[1]: Starting Docker Socket for the API. 
-- Subject: Unit docker.socket has begun start-up 
-- Defined-By: systemd 
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel 
-- 
-- Unit docker.socket has begun starting up. 
Jun 29 16:10:41 searchtest systemd[1]: Listening on Docker Socket for the API. 
-- Subject: Unit docker.socket has finished start-up 
-- Defined-By: systemd 
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel 
-- 
-- Unit docker.socket has finished starting up. 
-- 
-- The start-up result is done. 
Jun 29 16:10:41 searchtest systemd[1]: docker.service: Start request repeated too quickly. 
Jun 29 16:10:41 searchtest systemd[1]: Failed to start Docker Application Container Engine. 
-- Subject: Unit docker.service has failed 
-- Defined-By: systemd 
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel 
-- 
-- Unit docker.service has failed. 
-- 
-- The result is failed. 

Answer 2

Il semble qu'il y ait un bug dans la version Docker qui a été le déploiement d'hier. Une solution de contournement pour nous:

docker-machine create --driver amazonec2 --engine-install-url=https://web.archive.org/web/20170623081500/https://get.docker.com