create_docker_machine is nothing but the following:
docker-machine create \
--driver digitalocean \
--digitalocean-access-token... \
--digitalocean-region "fra1" \
--digitalocean-size "4gb" \
dockerHostFra2
The command above was working fine for months, but no longer works. Can anyone else reproduce, any suggestions?
$ ./create_docker_machine.sh
Running pre-create checks...
Creating machine...
(dockerHostFra2) Creating SSH key...
(dockerHostFra2) Creating Digital Ocean droplet...
(dockerHostFra2) Waiting for IP address to be assigned to the Droplet...
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.
$ docker-machine ssh dockerHostFra2
Welcome to Ubuntu 16.04.2 LTS (GNU/Linux 4.4.0-81-generic x86_64)
* Documentation: https://help.ubuntu.com
* Management: https://landscape.canonical.com
* Support: https://ubuntu.com/advantage
Get cloud support with Ubuntu Advantage Cloud Guest:
http://www.ubuntu.com/business/services/cloud
35 packages can be updated.
18 updates are security updates.
root@dockerHostFra2:~# 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 Mon 2017-07-10 08:13:03 UTC; 24s ago
Docs: https://docs.docker.com
Process: 4929 ExecStart=/usr/bin/docker daemon -H tcp://0.0.0.0:2376 -H unix:///var/run/docker.sock --storage-driver aufs --tl
Main PID: 4929 (code=exited, status=1/FAILURE)
Jul 10 08:13:03 dockerHostFra2 systemd[1]: Failed to start Docker Application Container Engine.
Jul 10 08:13:03 dockerHostFra2 systemd[1]: docker.service: Unit entered failed state.
Jul 10 08:13:03 dockerHostFra2 systemd[1]: docker.service: Failed with result 'exit-code'.
Jul 10 08:13:03 dockerHostFra2 systemd[1]: docker.service: Service hold-off time over, scheduling restart.
Jul 10 08:13:03 dockerHostFra2 systemd[1]: Stopped Docker Application Container Engine.
Jul 10 08:13:03 dockerHostFra2 systemd[1]: docker.service: Start request repeated too quickly.
Jul 10 08:13:03 dockerHostFra2 systemd[1]: Failed to start Docker Application Container Engine.
root@dockerHostFra2:~# journalctl -xe
--
-- The start-up result is done.
Jul 10 08:13:22 dockerHostFra2 systemd[4939]: Reached target Paths.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has finished starting up.
--
-- The start-up result is done.
Jul 10 08:13:22 dockerHostFra2 systemd[4939]: Reached target Basic System.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has finished starting up.
--
-- The start-up result is done.
Jul 10 08:13:22 dockerHostFra2 systemd[4939]: Reached target Default.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has finished starting up.
--
-- The start-up result is done.
Jul 10 08:13:22 dockerHostFra2 systemd[4939]: Startup finished in 29ms.
-- Subject: System start-up is now complete
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- All system services necessary queued for starting at boot have been
-- successfully started. Note that this does not mean that the machine is
-- now idle as services might still be busy with completing start-up.
--
-- Kernel start-up required KERNEL_USEC microseconds.
--
-- Initial RAM disk start-up required INITRD_USEC microseconds.
--
-- Userspace start-up required 29027 microseconds.
Jul 10 08:13:22 dockerHostFra2 systemd[1]: Started User Manager for UID 0.
-- Subject: Unit user@0.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit user@0.service has finished starting up.
--
-- The start-up result is done.
Jul 10 08:13:40 dockerHostFra2 sshd[4989]: Invalid user deploy from 111.207.49.189
Jul 10 08:13:40 dockerHostFra2 sshd[4989]: input_userauth_request: invalid user deploy [preauth]
Jul 10 08:13:41 dockerHostFra2 sshd[4989]: Connection closed by 111.207.49.189 port 54360 [preauth]