I'd like to register a Debian 8 box in cloud.docker.com but failed. It's always "Waiting for contact from agent". Then, I did try to reinstall the latest dockercloud-agent, reviewed the config file, the run the agent in standalone mode.

dockercloud-agent -standalone -stdout
2016/05/22 23:23:52 Running dockercloud-agent: version 1.1.0
2016/05/22 23:23:52 Create pid file(/var/run/dockercloud-agent.pid): 10123
2016/05/22 23:23:52 Checking if config file exists
2016/05/22 23:23:52 Loading Configuration file
2016/05/22 23:23:53 New TLS certificates generated
2016/05/22 23:23:53 Downloading docker binary...
2016/05/22 23:23:53 Downloading docker definition from
2016/05/22 23:23:53 Cannot get target definition: Get : unsupported protocol scheme "". Retry in 1 second
2016/05/22 23:23:54 Cannot get target definition: Get : unsupported protocol scheme "". Retry in 2 second
2016/05/22 23:23:56 Cannot get target definition: Get : unsupported protocol scheme "". Retry in 4 second
2016/05/22 23:24:00 Cannot get target definition: Get : unsupported protocol scheme "". Retry in 8 second
2016/05/22 23:24:08 Cannot get target definition: Get : unsupported protocol scheme "". Retry in 16 second

I am not able to upgrade to version 1.11 due to docker cloud agent having a dependency on docker version 1.9,

Is there any way to get around this ?

HI,

I have created a EC2 node from docker cloud. I tried to modify the default security group to allow the below ports:

UDP 6783 0.0.0.0
TCP 6783 0.0.0.0
TCP 2375 0.0.0.0
TCP 22 0.0.0.0
TCP 80 0.0.0.0
TCP 443 0.0.0.0

Initially there were no issues but after sometimes the server became unreachable. I had to open all the ports to make docker cloud work again. In this context, kindly let me know what all port is to be opened for docker cloud to work with AWS?

Regards,
Vijay Raajaa G S

Sorry, but I run this and killed my docker-machine "docker-engine" process, more over uninstallation was a pain. My server went completely down without this warning me.

Edit my /etc/default/docker file with the -g option does not work any more.

Gentoo Linux (the only true server linux distro) is not supported by Docker Cloud currently. There's also no dockercloud-agent in repos (both official and docker layman repo). I've done several manual attempts to build it from sources, but seems there's some dependency mess.
I guess it should be relatively easy to run it from docker container, but since I believe there's hard interaction with host machine docker itself would anybody help me running it this way? passing -v /var/run/docker.sock:/var/lib/docker.sock won't help?

Hello,

When I try to bring my own node I always get an error from the docker cloud UI (cloud.docker.com).

Here is the docker.log :

time="2016-09-26T22:00:24.099749274Z" level=info msg="Processing signal 'terminated'"
time="2016-09-26T22:00:24Z" level=info msg="stopping containerd after receiving terminated"
time="2016-09-26T22:00:24.101499856Z" level=info msg="Processing signal 'terminated'"
time="2016-09-26T22:00:31.644757771Z" level=info msg="New containerd process, pid: 14391\n"
time="2016-09-26T22:00:32.658172538Z" level=info msg="[graphdriver] using prior storage driver \"overlay\""
time="2016-09-26T22:00:32.684694650Z" level=info msg="Graph migration to content-addressability took 0.00 seconds"
time="2016-09-26T22:00:32.694096965Z" level=info msg="Firewalld running: false"
time="2016-09-26T22:00:32.948586608Z" level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address"
time="2016-09-26T22:00:33.123873111Z" level=warning msg="Your kernel does not support cgroup cfs period"
time="2016-09-26T22:00:33.124029051Z" level=warning msg="Your kernel does not support cgroup cfs quotas"
time="2016-09-26T22:00:33.124840016Z" level=info msg="Loading containers: start."

time="2016-09-26T22:00:33.125049560Z" level=info msg="Loading containers: done."
time="2016-09-26T22:00:33.125154552Z" level=info msg="Daemon has completed initialization"
time="2016-09-26T22:00:33.125214582Z" level=info msg="Docker daemon" commit=bfd1f99 graphdriver=overlay version=1.11.1-cs1
time="2016-09-26T22:00:33.161802916Z" level=info msg="API listen on [::]:2375"
time="2016-09-26T22:00:33.162040188Z" level=info msg="API listen on /var/run/docker.sock"
2016/09/26 22:00:33 http: TLS handshake error from 52.6.30.174:15683: EOF
2016/09/26 22:00:36 http: TLS handshake error from 52.6.30.174:51209: EOF
2016/09/26 22:00:36 http: TLS handshake error from 52.6.30.174:34670: EOF
2016/09/26 22:00:37 http: TLS handshake error from 52.6.30.174:65411: EOF
2016/09/26 22:00:37 http: TLS handshake error from 52.6.30.174:34438: EOF
2016/09/26 22:00:38 http: TLS handshake error from 52.6.30.174:38583: EOF
time="2016-09-26T22:00:41.525309998Z" level=error msg="Clean up Error! Cannot destroy container 76a1174ad179a40e0b79c5da27016e18b1446936ef8fa3129b0fd42ad8dc3e15: No such container: 76a1174ad179a40e0b79c5da27016e18b1446936ef8fa3129b0fd42ad8dc3e15"
time="2016-09-26T22:00:41.525534960Z" level=error msg="Handler for POST /v1.22/containers/create returned error: open /var/lib/docker/overlay/eeb43b47412d9541a2cef193619716ed262d427d3eaaec126c84b3b4d5c0c113-init/merged/dev/console: operation not permitted"
time="2016-09-26T22:00:42.712112003Z" level=error msg="Handler for POST /v1.22/containers/create returned error: Conflict. The name \"/weave-35171.b6124048\" is already in use by container 76a1174ad179a40e0b79c5da27016e18b1446936ef8fa3129b0fd42ad8dc3e15. You have to remove (or rename) that container to be able to reuse that name."
time="2016-09-26T22:00:43.894844987Z" level=error msg="Handler for POST /v1.22/containers/create returned error: Conflict. The name \"/weave-35171.b6124048\" is already in use by container 76a1174ad179a40e0b79c5da27016e18b1446936ef8fa3129b0fd42ad8dc3e15. You have to remove (or rename) that container to be able to reuse that name."

All the required ports are open.

uname -a : Linux scw-938d6b 4.5.1-std-1 #1 SMP Mon Apr 18 19:58:58 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Thanks for your help.

Hi,

We're planning to run dockercloud on some BYONs behind a firewall in our datacenter, so I'm doing some tests to see if it's going to work. I'm running vagrant/virtualbox on my laptop, ubuntu trusty 64 (14.04).

vagrant init ubuntu/trusty64
vagrant up
vagrant ssh
$ curl -Ls https://get.cloud.docker.com/ | sudo -H sh -s <big-long-key>

The agent took about 5 minutes, but eventually turned up in the Nodes tab in the Docker Cloud UI. All good. I shut the vagrant box down for the evening. Next morning I started the box up again, hoping that it would reconnect, it didn't, showing me the error Node registration to https://cloud.docker.com/ timed out in the logs.

What's weird is that the /var/log/dockercloud/ngrok.log shows that the periodic ping/pongs are working, giving the impression that a connection has been established.

I'm confused because it did work once, but has failed repeatedly since. I have verified that the box can curl https://cloud.docker.com/ successfully. I think it's pretty important to be able to restart a box and for it to reconnect.

The interesting part of /var/log/dockercloud/agent.log:

2016/09/07 07:08:04 Docker daemon (PID:1161) has been started
2016/09/07 07:08:06 Docker unix socket opened
2016/09/07 07:08:08 Node a7291e41-7537-4415-8e8d-0817d2b5e104.node.dockerapp.io is NOT publicly reachable
2016/09/07 07:08:08 Ngrok server: tunnel02.cloud.docker.com:4443
2016/09/07 07:08:08 Starting NAT tunnel
2016/09/07 07:08:09 Found new tunnel: tcp://tunnel02.cloud.docker.com:59835
2016/09/07 07:08:09 Sending tunnel address to Docker Cloud
2016/09/07 07:08:09 New tunnel has been set up
2016/09/07 07:13:04 Node registration to https://cloud.docker.com/ timed out
2016/09/07 07:13:04 Node state: Unreachable

The whole of /var/log/dockercloud/agent.log showing the successful initial connection:

2016/09/06 19:22:50 Running dockercloud-agent: version 1.1.0
2016/09/06 19:22:50 Create pid file(/var/run/dockercloud-agent.pid): 14826
2016/09/06 19:22:50 Checking if config file exists
2016/09/06 19:22:50 Loading Configuration file
2016/09/06 19:22:50 Registering in Docker Cloud via POST: https://cloud.docker.com/api/agent/v1/node/
2016/09/06 19:22:51 Cert CommonName has been changed from  to a7291e41-7537-4415-8e8d-0817d2b5e104.node.dockerapp.io
2016/09/06 19:22:51 UUID has been changed from  to a7291e41-7537-4415-8e8d-0817d2b5e104
2016/09/06 19:22:51 Updating configuration file...
2016/09/06 19:22:52 New TLS certificates generated
2016/09/06 19:22:52 Registering in Docker Cloud via PATCH: https://cloud.docker.com/api/agent/v1/node/a7291e41-7537-4415-8e8d-0817d2b5e104
2016/09/06 19:22:52 Downloading docker binary...
2016/09/06 19:22:52 Downloading docker definition from https://cloud.docker.com/api/tutum/v1/agent/docker/1.11.1-cs1/1.1.0.json
2016/09/06 19:22:52 Downloading docker from https://files.cloud.docker.com/packages/docker/docker-1.11.1-cs1.tgz
2016/09/06 19:23:18 Saving docker to /usr/bin/
2016/09/06 19:23:18 Uncompressing: /usr/bin/docker-containerd-ctr
2016/09/06 19:23:18 Uncompressing: /usr/bin/docker-runc
2016/09/06 19:23:18 Uncompressing: /usr/bin/docker
2016/09/06 19:23:19 Uncompressing: /usr/bin/docker-containerd
2016/09/06 19:23:19 Uncompressing: /usr/bin/docker-containerd-shim
2016/09/06 19:23:19 Found docker: version 1.11.1-cs1
2016/09/06 19:23:19 Initializing docker daemon
2016/09/06 19:23:19 Loading NAT tunnel module
2016/09/06 19:23:19 Verifying the registration with Docker Cloud
2016/09/06 19:23:19 Docker server started. Entering maintenance loop
2016/09/06 19:23:19 Starting docker daemon: [/usr/bin/docker daemon -H unix:///var/run/docker.sock -H tcp://0.0.0.0:2375 --userland-proxy=false --tlscert /etc/dockercloud/agent/cert.pem --tlskey /etc/dockercloud/agent/key.pem --tlscacert /etc/dockercloud/agent/ca.pem --tlsverify]
2016/09/06 19:23:19 Waiting for docker unix socket to be ready
2016/09/06 19:23:19 Docker daemon (PID:15680) has been started
2016/09/06 19:23:21 Docker unix socket opened
2016/09/06 19:23:23 Node a7291e41-7537-4415-8e8d-0817d2b5e104.node.dockerapp.io is NOT publicly reachable
2016/09/06 19:23:23 Downloading NAT tunnel binary ...
2016/09/06 19:23:23 Downloading ngrok definition from https://cloud.docker.com/api/tutum/v1/agent/ngrok/latest/1.1.0.json
2016/09/06 19:23:24 Downloading ngrok from https://files.cloud.docker.com/packages/ngrok/ngrok-1.7.tgz
2016/09/06 19:23:29 Saving ngrok to /usr/lib/dockercloud/
2016/09/06 19:23:29 Uncompressing: /usr/lib/dockercloud/._ngrok
2016/09/06 19:23:29 Uncompressing: /usr/lib/dockercloud/ngrok
2016/09/06 19:23:29 Ngrok server: tunnel02.cloud.docker.com:4443
2016/09/06 19:23:29 Starting NAT tunnel
2016/09/06 19:23:31 Found new tunnel: tcp://tunnel02.cloud.docker.com:41790
2016/09/06 19:23:31 Sending tunnel address to Docker Cloud
2016/09/06 19:23:31 New tunnel has been set up
2016/09/06 19:28:20 Node registration to https://cloud.docker.com/ succeeded
2016/09/06 19:30:02 Got signal: terminated
2016/09/06 19:30:02 Docker daemon is running
2016/09/06 19:30:02 Starting to shut down docker daemon gracefully
2016/09/06 19:30:02 Scheduling for shutting down, do not restart the tunnel
2016/09/07 07:08:02 Running dockercloud-agent: version 1.1.0
2016/09/07 07:08:02 Create pid file(/var/run/dockercloud-agent.pid): 854
2016/09/07 07:08:02 Checking if config file exists
2016/09/07 07:08:02 Loading Configuration file
2016/09/07 07:08:02 Registering in Docker Cloud via PATCH: https://cloud.docker.com/api/agent/v1/node/a7291e41-7537-4415-8e8d-0817d2b5e104
2016/09/07 07:08:04 Found docker: version 1.11.1-cs1
2016/09/07 07:08:04 Initializing docker daemon
2016/09/07 07:08:04 Loading NAT tunnel module
2016/09/07 07:08:04 Verifying the registration with Docker Cloud
2016/09/07 07:08:04 Docker server started. Entering maintenance loop
2016/09/07 07:08:04 Waiting for docker unix socket to be ready
2016/09/07 07:08:04 Starting docker daemon: [/usr/bin/docker daemon -H unix:///var/run/docker.sock -H tcp://0.0.0.0:2375 --userland-proxy=false --tlscert /etc/dockercloud/agent/cert.pem --tlskey /etc/dockercloud/agent/key.pem --tlscacert /etc/dockercloud/agent/ca.pem --tlsverify]
2016/09/07 07:08:04 Docker daemon (PID:1161) has been started
2016/09/07 07:08:06 Docker unix socket opened
2016/09/07 07:08:08 Node a7291e41-7537-4415-8e8d-0817d2b5e104.node.dockerapp.io is NOT publicly reachable
2016/09/07 07:08:08 Ngrok server: tunnel02.cloud.docker.com:4443
2016/09/07 07:08:08 Starting NAT tunnel
2016/09/07 07:08:09 Found new tunnel: tcp://tunnel02.cloud.docker.com:59835
2016/09/07 07:08:09 Sending tunnel address to Docker Cloud
2016/09/07 07:08:09 New tunnel has been set up
2016/09/07 07:13:04 Node registration to https://cloud.docker.com/ timed out
2016/09/07 07:13:04 Node state: Unreachable

I'd like to ask how does the dockercloud-agent relate to docker swarm, and can a swarm cluster be brought into docker cloud? (I'm assuming yes, due to seeing "node clusters" in the gui)

If yes, what would that process be, and is it documented anywhere?

am I really the first one or it's not the right place?

tried latest docker-cloud by installing the dockercloud-agent according to documentation.
in Tutum it worked fine when following the guidelines to connect between a service in one stack to one in another (via service_name.stack_name).
With docker cloud we keep getting 127.0.53.53 as a hint that the DNS agent actually goes to some public DNS instead of resolving the names internally. ping from withing the container to other containers/service names within the stack works fine.

docker version 1.9.1-cs2, build 4ade326 (the dockercloud-agent installed it I believe)

I was wondering if there are any plans to bring dockercloud-agent to Ubuntu 16.04.

https://github.com/docker/dockercloud-agent/blob/v1.1.0/contrib/make-rpm.sh

after looking the contents i noticed bunch of debian specific things that are likely unhandled for redhat systems:

• post/pre-inst scripts will never do anything because $1 are numeric
• redhats never went for upstart, afaik only one version of fedora had upstart
• _dh_action is likely undefined
• #DEBHELPER# is noop
• postrm is never do anything due wrong $1 comparision
• postinst $2 check is incorrect, should be again $2 = 2 to ensure upgrade, not first install
• prerm $1 check also wrong, should be $1 = 0 to check uninstall otherwise you be stopping it on upgrades!
• shared library depends like --depends libc.so.6 are pointless because rpmbuild generates them, and incorrect because they lack x86_64 specifier. not sure about fpm
• --provides dockercloud-agent / --replaces dockercloud-agent is dumb, it's default behaviour of rpm to upgrade packages by same name.

as i read from your pull-request/tickets this tool will become soon obsolete, i did not bother to send PR, at least write Issue so you can decide yourself. i don't use redhat/rhel/fedora either so i'm no good tester.

Hi,
When do you plan support RPI ?

$ curl -Ls https://get.cloud.docker.com/ | sudo -H sh -s xxxx
ERROR: Unsupported architecture: armv7l
Only x86_64 architectures are supported at this time
Learn more: https://docs.docker.com/docker-cloud/tutorials/byoh/

Given the following scenario:

EC2 node deployed via Docker Cloud using t2.medium instance type. After changing the instance type to t2.large via AWS console (stop, change instance type, start) the WebUI continues to list node details for the old instance instance type.

The WebUI does receive a Node Update (agent) success event, which triggers the corresponding Container update events successfully. Details about the new instance type are available via the instance metadata (http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html#instancedata-data-retrieval)

Note: I have not tested this scenario with other providers (i.e. resizing a DigitalOcean droplet, though I suspect the flow should be fairly similar).

~$ service dockercloud-agent restart

the log;

2017/12/21 18:00:02 Running dockercloud-agent: version 1.1.0
2017/12/21 18:00:02 Create pid file(/var/run/dockercloud-agent.pid): <pid was here>
2017/12/21 18:00:02 Checking if config file exists
2017/12/21 18:00:02 Loading Configuration file
2017/12/21 18:00:02 Registering in Docker Cloud via PATCH: https://cloud.docker.com/api/agent/v1/node/<UUID was here>

Program infinitely hangs, which also hangs dockerd..

to reproduce;

• Install ubuntu-17.10-server-amd64
• Follow the steps to Bring your own node
• Notice much later the install finished and check the agent status on a new session;

~$ service dockercloud-agent status returns active (running)

• tail the log tail -f /var/log/dockercloud/agent.log and restart the agent service dockercloud-agent restart
• should show Registering in Docker Cloud via PATCH
• try to use Docker docker ps and notice it just hangs

I'm no expert at golang, but followign the log message from here
https://github.com/docker/dockercloud-agent/blob/d7eb171fcdf9a45b3fb5647cf862c7fda3ab83f0/agent.go#L72

to this call;
https://github.com/docker/dockercloud-agent/blob/d7eb171fcdf9a45b3fb5647cf862c7fda3ab83f0/agent/reg.go#L59

I don;t see the error from GetCertificate so i assume it passes ok, i don't see the error from json.Marshal so again i assume it passes ok, then register is returned;
https://github.com/docker/dockercloud-agent/blob/master/agent/reg.go#L123

which takes me to some loop where sendRegRequest is called and there is some complex err handling here i think it's here there is a black hole and the program has no options to continue or log.

EDIT:
also, after the hang occurs and you issue service dockercloud-agent stop and try to use docker commands it complains about /var/run/docker.sock No such file or directory
however it is fine;
ls -la /var/run/docker.sock
returns
srw-rw---- 1 root docker 0 Dec 21 19:22 /var/run/docker.sock

Doing a service docker restart fixes it, you can do whatever docker commands you like without any issues until you run service dockercloud-agent start when it hangs again, and if you run stop the docker cli complains about the .sock file as before.

I tried using journald in Docker Cloud Agent via editing the DockerOpts but when I tried docker logs --tail=100 -f <container_id> it returned Error response from daemon: configured logging reader does not support reading. I expected it to be readable via docker logs.

Is there any workaround to this?

PS
I am using journald as every redeploy of my containers truncates the logs

Hello Docker Team,

Docker Cloud does not save the option BUILD LOCATION in "Configure Automated Builds". When I set the option to "Build on my own Nodes" it does not persist. In the next CI Cycle, the container is getting build on docker servers in San Francisco. Could you please fix this.

I'm available for any further information 😃

Kindly regards, edudorus

Using: Ubuntu Trusty on dockercloud-agent 1.1.0.

How to reproduce:
Install the agent on a BYON (bring your own node) and then use the command sudo dockercloud-agent -debug. Restart the agent using sudo service dockercloud-agent restart. Open the logs and you will find that the agent does not detect that it neither has been restarted nor does it log a change in PID.

For example:

ubuntu@ubuntu5:~$ sudo dockercloud-agent -debug
[sudo] password for ubuntu:
ubuntu@ubuntu5:~$ sudo service dockercloud-agent restart
dockercloud-agent stop/waiting
dockercloud-agent start/running, process 11475 // note the PID here
ubuntu@ubuntu5:~$ tail -f /var/log/dockercloud/agent.log
2016/06/22 12:26:49 Found docker: version 1.9.1-cs2
2016/06/22 12:26:49 Initializing docker daemon
2016/06/22 12:26:49 Loading NAT tunnel module
2016/06/22 12:26:49 Verifying the registration with Docker Cloud
2016/06/22 12:26:49 Docker server started. Entering maintenance loop
2016/06/22 12:26:49 Waiting for docker unix socket to be ready
2016/06/22 12:26:49 Starting docker daemon: [/usr/bin/docker daemon -H unix:///var/run/docker.sock -H tcp://0.0.0.0:2375 --userland-proxy=false --tlscert /etc/dockercloud/agent/cert.pem --tlskey /etc/dockercloud/agent/key.pem --tlscacert /etc/dockercloud/agent/ca.pem --tlsverify]
2016/06/22 12:26:49 Docker daemon (PID:11517) has been started // note the PID here
2016/06/22 12:26:51 Docker unix socket opened
2016/06/22 12:26:51 Node abc123.node.dockerapp.io is publicly reachable

How can I configure the docker daemon run by dockercloud agent?

Hello, I'm having a strange issue:

# dockercloud-agent -debug -stdout

2017/08/07 15:45:36 Running dockercloud-agent: version 1.1.0
2017/08/07 15:45:36 Create pid file(/var/run/dockercloud-agent.pid): 3213
2017/08/07 15:45:36 Checking if config file exists
2017/08/07 15:45:36 Loading Configuration file
2017/08/07 15:45:36 Registering in Docker Cloud via PATCH: https://cloud.docker.com/api/agent/v1/node/5961f767-a461-4faa-a500-c56efb3221e2
2017/08/07 15:45:36 =======Request Info ======
2017/08/07 15:45:36 => URL: https://cloud.docker.com/api/agent/v1/node/5961f767-a461-4faa-a500-c56efb3221e2/
2017/08/07 15:45:36 => Method: PATCH
2017/08/07 15:45:36 => Headers: map[User-Agent:[dockercloud-agent/1.1.0] Authorization:[TutumAgentToken 94c38a61b1794d6d85e6edb8fa80fd1a] Content-Type:[application/json]]
2017/08/07 15:45:36 => Body: {"public_cert":"-----BEGIN CERTIFICATE-----\nMIID2DCCAsCgAwIBAgIRAM9wEICRCfHQWkwKvnREqYUwDQYJKoZIhvcNAQELBQAw\naTEmMCQGA1UEChMdRG9ja2VyIENsb3VkIFNlbGYtU2lnbmVkIEhvc3QxPzA9BgNV\nBAMTNjU5NjFmNzY3LWE0NjEtNGZhYS1hNTAwLWM1NmVmYjMyMjFlMi5ub2RlLmRv\nY2tlcmFwcC5pbzAeFw0xNzA4MDcxNTM1MDFaFw0yNzA4MDUxNTM1MDFaMGkxJjAk\nBgNVBAoTHURvY2tlciBDbG91ZCBTZWxmLVNpZ25lZCBIb3N0MT8wPQYDVQQDEzY1\nOTYxZjc2Ny1hNDYxLTRmYWEtYTUwMC1jNTZlZmIzMjIxZTIubm9kZS5kb2NrZXJh\ncHAuaW8wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDDQ58yz+/RKs9q\nd8nmR3G+NJqU+C4zUAPA71vp9NJYbHn/XaqyRuoEcZV6UMDPKTQzJMg8iMo4L42R\n+aA6S1sADW5IZvch9VbquGEzlnj0SgYpjhtlZ57kSMi3+a6LcpH60s3jiD4VcZgQ\nmslJF30tkGiSN9q+q7k/yDLWSqWtk/v/d6G+lzVmMXtwfaQEbyvwPVd8oSf5c57v\nGP8HJcyBzZKmEnV0bQJ2w0r+Sq0tqQGtEeN6WKUzE9DtwXu5b7C3wUBqabE7IgkI\nWLMNeZqR0sXVPTy5T1ivryzBNJaUThRZIhhtNtkW+w+4OCdeHDSDZuwppeezxWap\nF9SwTza/AgMBAAGjezB5MA4GA1UdDwEB/wQEAwICpDATBgNVHSUEDDAKBggrBgEF\nBQcDATAPBgNVHRMBAf8EBTADAQH/MEEGA1UdEQQ6MDiCNjU5NjFmNzY3LWE0NjEt\nNGZhYS1hNTAwLWM1NmVmYjMyMjFlMi5ub2RlLmRvY2tlcmFwcC5pbzANBgkqhkiG\n9w0BAQsFAAOCAQEAE6M1akA7+ckCAlAa/GTTRLCh03unyLqKAHziciySsSUnRkDi\nHU53uebHmQxSWQ0MoSrRH4zQgKim+64bkIIB5ekp6Isnuemp40vaRISj5k4syiA/\nATNUSW+VauXDuAckXpbVt1eR2coVBwzN6KtSbMr5tOG6ySx7cDpMdAHjMvo68O8j\n4sOWVG/KnMaRvtmM/AxR5L7NYj4dmpXsLIx7Kxr1oyAlwqmhjIPHEn3lsZ75KpaP\nxW5G9kg2tBxbCss5+nr0A4TdbXzz742xOPQJbHBS6AUM/QjO73nMW56Jp2RD+aF8\n39MSj+su/9pBwnZDFq99EFkRKDOu6eFV479VTw==\n-----END CERTIFICATE-----\n","agent_version":"1.1.0","docker_version":"17.06.0-ce"}
2017/08/07 15:45:37 =======Response Info (ERROR) ======
2017/08/07 15:45:37 => Headers: map[Date:[Mon, 07 Aug 2017 15:45:37 GMT] X-Content-Type-Options:[nosniff] X-Frame-Options:[deny] X-Ratelimit-Reset:[60] X-Xss-Protection:[1; mode=block] Server:[nginx] Content-Type:[application/json] Content-Length:[70] X-Ratelimit-Limit:[60] X-Ratelimit-Remaining:[59] Strict-Transport-Security:[max-age=31536000]]
2017/08/07 15:45:37 => Body: {"error": "{'node': {'docker_version': [u'Invalid docker version']}}"}
2017/08/07 15:45:37 Registration failed, 400. Retry in 1 seconds

# docker info
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 5
Server Version: 17.06.0-ce
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 13
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins: 
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: cfb82a876ecc11b5ca0977d1733adbe58599088a
runc version: 2d41c047c83e09a6d61d464906feb2a2f3c52aa4
init version: 949e6fa
Security Options:
 apparmor
 seccomp
  Profile: default
Kernel Version: 4.10.0-30-generic
Operating System: Ubuntu 16.04.3 LTS
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 31.12GiB
Name: dc-01-srv-01
ID: 7B42:FV5J:74R5:JEYC:TARX:SRHB:Y2IV:Z2FQ:CYV5:7U7X:ELPM:55QR
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false

WARNING: No swap limit support

I also noticed on the page (https://cloud.docker.com/app/clover/node/5961f767-a461-4faa-a500-c56efb3221e2/general) is shows DOCKER INFO Version 1.11.2-cs5.

Any ideas?

Hello,
I have two identical VPS servers that I would like to use as byo nodes in Docker Cloud. While one of them registered successfully in Docker cloud, the other one keeps trying to register and failing. /var/log/agent.log shows Registration failed, 402. Trying again in 8s, 16s, 32s...

W: http://repo.cloud.docker.com/ubuntu/dists/dockercloud/InRelease: Signature by key 278FE7333CFF7F8B60B677E85DD27147EF170D1C uses weak digest algorithm (SHA1)

Environment: Ubuntu Trusty 14.04 on agent 1.1.0.

Using Docker Cloud Bring Your Own Node (BYON). We have some private infrastructure set up behind a router, and none of our nodes have a public IP. The firewall is turned off in each node.

It would appear that the dockercloud-agent is unable to set up a reverse tunnel from our private infrastructure. I've browsed the documentation extensively to determine the settings for our nodes, and as far as I can see we are following everything properly. The only difference is that each node does not have a public IP. Can someone please help clarify what settings need to be in place for a setup like ours?

Below is an example of a typical BYON setup:

2016/06/22 11:13:48 UUID has been changed from  to blahblahabc123
2016/06/22 11:13:48 Updating configuration file...
2016/06/22 11:13:48 New TLS certificates generated
2016/06/22 11:13:48 Registering in Docker Cloud via PATCH: https://cloud.docker.com/api/agent/v1/node/blahblahabc123
2016/06/22 11:13:49 Downloading docker binary...
2016/06/22 11:13:49 Downloading docker definition from https://cloud.docker.com/api/tutum/v1/agent/docker/1.9.1-cs2/1.1.0.json
2016/06/22 11:13:49 Downloading docker from https://files.cloud.docker.com/packages/docker/docker-1.9.1-cs2.tgz
2016/06/22 11:13:50 Saving docker to /usr/bin/
2016/06/22 11:13:50 Uncompressing: /usr/bin/._docker
2016/06/22 11:13:50 Uncompressing: /usr/bin/docker
2016/06/22 11:13:51 Found docker: version 1.9.1-cs2
2016/06/22 11:13:51 Initializing docker daemon
2016/06/22 11:13:51 Loading NAT tunnel module
2016/06/22 11:13:51 Verifying the registration with Docker Cloud
2016/06/22 11:13:51 Docker server started. Entering maintenance loop
2016/06/22 11:13:51 Waiting for docker unix socket to be ready
2016/06/22 11:13:51 Starting docker daemon: [/usr/bin/docker daemon -H unix:///var/run/docker.sock -H tcp://0.0.0.0:2375 --userland-proxy=false --tlscert /etc/dockercloud/agent/cert.pem --tlskey /etc/dockercloud/agent/key.pem --tlscacert /etc/dockercloud/agent/ca.pem --tlsverify]
2016/06/22 11:13:51 Docker daemon (PID:2598) has been started
2016/06/22 11:13:53 Docker unix socket opened
2016/06/22 11:13:53 Node blahblahabc123.node.dockerapp.io is publicly reachable
2016/06/22 11:18:55 Node registration to https://cloud.docker.com/ succeeded

Note above what we had to do here was deploy the node, and it appears the NAT tunnel for a moment started to set itself up. However after waiting 5 minutes, we opened 2375/tcp from our router only to then have the node publicly reachable. However, even after we close 2375/tcp Docker Cloud thinks the node is unreachable but the node itself fails to detect this in state. If we don't open port 2375, Docker Cloud will instead auto-terminate the node.

Thanks for your help!

Trying to work around this issue (#18), looks like I exposed another one...

When I look at my /etc/dockercloud/agent/dockercloud-agent.conf it is clearly filled in with info, and this is after I set the token using dockercloud-agent set Token=xxxxx.

{"CertCommonName":"","DockerHost":"tcp://0.0.0.0:2375","Host":"https://cloud.docker.com/","Token":"xxxxx","UUID":"","DockerOpts":""}

However, each time I run sudo service dockercloud-agent start it erases the config back to this, causing the error in the following log and preventing startup:

{"CertCommonName":"","DockerHost":"tcp://0.0.0.0:2375","Host":"https://cloud.docker.com/","Token":"","UUID":"","DockerOpts":""}

Logfile:

2016/06/22 17:18:12 Checking if config file exists
2016/06/22 17:18:12 Loading Configuration file
2016/06/22 17:18:12 Registering in Docker Cloud via POST: https://cloud.docker.com/api/agent/v1/node/
2016/06/22 17:18:12 The token is empty. Please run 'dockercloud-agent set Token=xxx' first!
2016/06/22 17:18:12 Running dockercloud-agent: version 1.1.0
2016/06/22 17:18:12 Create pid file(/var/run/dockercloud-agent.pid): 1781
2016/06/22 17:18:12 Checking if config file exists
2016/06/22 17:18:12 Loading Configuration file
2016/06/22 17:18:12 Registering in Docker Cloud via POST: https://cloud.docker.com/api/agent/v1/node/
2016/06/22 17:18:12 The token is empty. Please run 'dockercloud-agent set Token=xxx' first!

Hello, I have worked with docker cloud for a month. My nodes are created as described at https://docs.docker.com/docker-cloud/infrastructure/link-do/ for a Digital Ocean account. But I've decided to update the operating system of the node (I access through ssh https://docs.docker.com/docker-cloud/infrastructure/ssh-into-a-node/)
$ sudo apt update && sudo apt upgrade

Then increase the swap memory as described here: https://www.digitalocean.com/community/tutorials/how-to-add-swap-on-ubuntu-14-04

I finally reboot the system:
$ sudo reboot

But after this my system is already inaccessible from Docker cloud as shown in the image.

When running
$ docker version
I get:

Docker version 
Client: 
 Version: 1.11.2-cs5 
 API version: 1.23 
 Go version: go1.5.4 
 Git commit: d364ea1 
 Built: Tue Sep 13 15:26:43 2016 
 OS / Arch: linux / amd64 
Can not connect to the Docker daemon. Is the docker daemon running on this host?

log /var/log/dockercloud/agent.log

2016/12/21 15:58:56 Got signal: terminated
2016/12/21 15:58:56 Docker daemon is running
2016/12/21 15:58:56 Starting to shut down docker daemon gracefully
2016/12/21 15:59:26 Running dockercloud-agent: version 1.1.0
2016/12/21 15:59:26 Create pid file(/var/run/dockercloud-agent.pid): 1166
2016/12/21 15:59:26 Checking if config file exists
2016/12/21 15:59:26 Loading Configuration file
2016/12/21 15:59:26 Registering in Docker Cloud via PATCH: https://cloud.docker.com/api/agent/v1/node/7b74789b-ba06-427b-b3ed-b548466d949d
2016/12/21 15:59:27 PATCH error 401 :either UUID (7b74789b-ba06-427b-b3ed-b548466d949d) or Token is invalid
2016/12/21 15:59:27 Registering in Docker Cloud via POST: https://cloud.docker.com/api/agent/v1/node/
2016/12/21 15:59:27 Cannot register node in Docker Cloud: unauthorized. Please try again with a new token.
2016/12/21 15:59:27 Removing the invalid token from config file
2016/12/21 15:59:37 Docker Cloud agent is terminated
2016/12/21 15:59:37 Running dockercloud-agent: version 1.1.0
2016/12/21 15:59:37 Create pid file(/var/run/dockercloud-agent.pid): 1820
2016/12/21 15:59:37 Checking if config file exists
2016/12/21 15:59:37 Loading Configuration file
2016/12/21 15:59:37 Registering in Docker Cloud via POST: https://cloud.docker.com/api/agent/v1/node/
2016/12/21 15:59:37 The token is empty. Please run 'dockercloud-agent set Token=xxx' first!
2016/12/21 15:59:37 Running dockercloud-agent: version 1.1.0
2016/12/21 15:59:37 Create pid file(/var/run/dockercloud-agent.pid): 1860
2016/12/21 15:59:37 Checking if config file exists
2016/12/21 15:59:37 Loading Configuration file
2016/12/21 15:59:37 Registering in Docker Cloud via POST: https://cloud.docker.com/api/agent/v1/node/
2016/12/21 15:59:37 The token is empty. Please run 'dockercloud-agent set Token=xxx' first!
2016/12/21 15:59:37 Running dockercloud-agent: version 1.1.0
2016/12/21 15:59:37 Create pid file(/var/run/dockercloud-agent.pid): 1902
2016/12/21 15:59:37 Checking if config file exists
2016/12/21 15:59:37 Loading Configuration file
2016/12/21 15:59:37 Registering in Docker Cloud via POST: https://cloud.docker.com/api/agent/v1/node/
2016/12/21 15:59:37 The token is empty. Please run 'dockercloud-agent set Token=xxx' first!
2016/12/21 16:24:01 Running dockercloud-agent: version 1.1.0
2016/12/21 16:24:01 Create pid file(/var/run/dockercloud-agent.pid): 2259
2016/12/21 16:24:01 Checking if config file exists
2016/12/21 16:24:01 Loading Configuration file
2016/12/21 16:24:01 Registering in Docker Cloud via POST: https://cloud.docker.com/api/agent/v1/node/
2016/12/21 16:24:01 The token is empty. Please run 'dockercloud-agent set Token=xxx' first!
2016/12/21 16:31:49 Running dockercloud-agent: version 1.1.0
2016/12/21 16:31:49 Create pid file(/var/run/dockercloud-agent.pid): 2319
2016/12/21 16:31:49 Checking if config file exists
2016/12/21 16:31:49 Loading Configuration file
2016/12/21 16:31:49 Registering in Docker Cloud via POST: https://cloud.docker.com/api/agent/v1/node/
2016/12/21 16:31:49 The token is empty. Please run 'dockercloud-agent set Token=xxx' first!
2016/12/21 16:31:50 Running dockercloud-agent: version 1.1.0
2016/12/21 16:31:50 Create pid file(/var/run/dockercloud-agent.pid): 2359
2016/12/21 16:31:50 Checking if config file exists
2016/12/21 16:31:50 Loading Configuration file
2016/12/21 16:31:50 Registering in Docker Cloud via POST: https://cloud.docker.com/api/agent/v1/node/
2016/12/21 16:31:50 The token is empty. Please run 'dockercloud-agent set Token=xxx' first!
2016/12/21 16:31:50 Running dockercloud-agent: version 1.1.0
2016/12/21 16:31:50 Create pid file(/var/run/dockercloud-agent.pid): 2399
2016/12/21 16:31:50 Checking if config file exists
2016/12/21 16:31:50 Loading Configuration file
2016/12/21 16:31:50 Registering in Docker Cloud via POST: https://cloud.docker.com/api/agent/v1/node/
2016/12/21 16:31:50 The token is empty. Please run 'dockercloud-agent set Token=xxx' first!
2016/12/21 16:31:50 Running dockercloud-agent: version 1.1.0
2016/12/21 16:31:50 Create pid file(/var/run/dockercloud-agent.pid): 2441
2016/12/21 16:31:50 Checking if config file exists
2016/12/21 16:31:50 Loading Configuration file
2016/12/21 16:31:50 Registering in Docker Cloud via POST: https://cloud.docker.com/api/agent/v1/node/
2016/12/21 16:31:50 The token is empty. Please run 'dockercloud-agent set Token=xxx' first!
2016/12/21 16:32:03 Running dockercloud-agent: version 1.1.0
2016/12/21 16:32:03 Create pid file(/var/run/dockercloud-agent.pid): 2494
2016/12/21 16:32:03 Checking if config file exists
2016/12/21 16:32:03 Loading Configuration file
2016/12/21 16:32:03 Registering in Docker Cloud via POST: https://cloud.docker.com/api/agent/v1/node/
2016/12/21 16:32:03 The token is empty. Please run 'dockercloud-agent set Token=xxx' first!
2016/12/21 16:32:03 Running dockercloud-agent: version 1.1.0
2016/12/21 16:32:03 Create pid file(/var/run/dockercloud-agent.pid): 2534
2016/12/21 16:32:03 Checking if config file exists
2016/12/21 16:32:03 Loading Configuration file
2016/12/21 16:32:03 Registering in Docker Cloud via POST: https://cloud.docker.com/api/agent/v1/node/
2016/12/21 16:32:03 The token is empty. Please run 'dockercloud-agent set Token=xxx' first!
2016/12/21 16:32:03 Running dockercloud-agent: version 1.1.0
2016/12/21 16:32:03 Create pid file(/var/run/dockercloud-agent.pid): 2574
2016/12/21 16:32:03 Checking if config file exists
2016/12/21 16:32:03 Loading Configuration file
2016/12/21 16:32:03 Registering in Docker Cloud via POST: https://cloud.docker.com/api/agent/v1/node/
2016/12/21 16:32:03 The token is empty. Please run 'dockercloud-agent set Token=xxx' first!
2016/12/21 16:32:03 Running dockercloud-agent: version 1.1.0
2016/12/21 16:32:03 Create pid file(/var/run/dockercloud-agent.pid): 2614
2016/12/21 16:32:03 Checking if config file exists
2016/12/21 16:32:03 Loading Configuration file
2016/12/21 16:32:03 Registering in Docker Cloud via POST: https://cloud.docker.com/api/agent/v1/node/
2016/12/21 16:32:03 The token is empty. Please run 'dockercloud-agent set Token=xxx' first!
2016/12/21 16:32:59 Running dockercloud-agent: version 1.1.0
2016/12/21 16:32:59 Create pid file(/var/run/dockercloud-agent.pid): 2631
2016/12/21 16:32:59 Checking if config file exists
2016/12/21 16:32:59 Loading Configuration file
2016/12/21 16:32:59 Registering in Docker Cloud via POST: https://cloud.docker.com/api/agent/v1/node/
2016/12/21 16:32:59 The token is empty. Please run 'dockercloud-agent set Token=xxx' first!
2016/12/21 16:34:36 Running dockercloud-agent: version 1.1.0
2016/12/21 16:34:36 Create pid file(/var/run/dockercloud-agent.pid): 2676
2016/12/21 16:34:36 Checking if config file exists
2016/12/21 16:34:36 Loading Configuration file
2016/12/21 16:34:36 Registering in Docker Cloud via POST: https://cloud.docker.com/api/agent/v1/node/
2016/12/21 16:34:36 The token is empty. Please run 'dockercloud-agent set Token=xxx' first!
2016/12/21 16:34:36 Running dockercloud-agent: version 1.1.0
2016/12/21 16:34:36 Create pid file(/var/run/dockercloud-agent.pid): 2717
2016/12/21 16:34:36 Checking if config file exists
2016/12/21 16:34:36 Loading Configuration file
2016/12/21 16:34:36 Registering in Docker Cloud via POST: https://cloud.docker.com/api/agent/v1/node/
2016/12/21 16:34:36 The token is empty. Please run 'dockercloud-agent set Token=xxx' first!
2016/12/21 16:34:36 Running dockercloud-agent: version 1.1.0
2016/12/21 16:34:36 Create pid file(/var/run/dockercloud-agent.pid): 2758
2016/12/21 16:34:36 Checking if config file exists
2016/12/21 16:34:36 Loading Configuration file
2016/12/21 16:34:36 Registering in Docker Cloud via POST: https://cloud.docker.com/api/agent/v1/node/
2016/12/21 16:34:36 The token is empty. Please run 'dockercloud-agent set Token=xxx' first!
2016/12/21 16:34:36 Running dockercloud-agent: version 1.1.0
2016/12/21 16:34:36 Create pid file(/var/run/dockercloud-agent.pid): 2799
2016/12/21 16:34:36 Checking if config file exists
2016/12/21 16:34:36 Loading Configuration file
2016/12/21 16:34:36 Registering in Docker Cloud via POST: https://cloud.docker.com/api/agent/v1/node/
2016/12/21 16:34:36 The token is empty. Please run 'dockercloud-agent set Token=xxx' first!
2016/12/21 16:54:29 Running dockercloud-agent: version 1.1.0
2016/12/21 16:54:29 Create pid file(/var/run/dockercloud-agent.pid): 1164
2016/12/21 16:54:29 Checking if config file exists
2016/12/21 16:54:29 Loading Configuration file
2016/12/21 16:54:29 Registering in Docker Cloud via POST: https://cloud.docker.com/api/agent/v1/node/
2016/12/21 16:54:29 The token is empty. Please run 'dockercloud-agent set Token=xxx' first!
2016/12/21 16:54:30 Running dockercloud-agent: version 1.1.0
2016/12/21 16:54:30 Create pid file(/var/run/dockercloud-agent.pid): 1300
2016/12/21 16:54:30 Checking if config file exists
2016/12/21 16:54:30 Loading Configuration file
2016/12/21 16:54:30 Registering in Docker Cloud via POST: https://cloud.docker.com/api/agent/v1/node/
2016/12/21 16:54:30 The token is empty. Please run 'dockercloud-agent set Token=xxx' first!
2016/12/21 16:54:30 Running dockercloud-agent: version 1.1.0
2016/12/21 16:54:30 Create pid file(/var/run/dockercloud-agent.pid): 1395
2016/12/21 16:54:30 Checking if config file exists
2016/12/21 16:54:30 Loading Configuration file
2016/12/21 16:54:30 Registering in Docker Cloud via POST: https://cloud.docker.com/api/agent/v1/node/
2016/12/21 16:54:30 The token is empty. Please run 'dockercloud-agent set Token=xxx' first!
2016/12/21 16:54:31 Running dockercloud-agent: version 1.1.0
2016/12/21 16:54:31 Create pid file(/var/run/dockercloud-agent.pid): 1560
2016/12/21 16:54:31 Checking if config file exists
2016/12/21 16:54:31 Loading Configuration file
2016/12/21 16:54:31 Registering in Docker Cloud via POST: https://cloud.docker.com/api/agent/v1/node/
2016/12/21 16:54:31 The token is empty. Please run 'dockercloud-agent set Token=xxx' first!
2016/12/21 16:54:31 Running dockercloud-agent: version 1.1.0
2016/12/21 16:54:31 Create pid file(/var/run/dockercloud-agent.pid): 1652
2016/12/21 16:54:31 Checking if config file exists
2016/12/21 16:54:31 Loading Configuration file
2016/12/21 16:54:31 Registering in Docker Cloud via POST: https://cloud.docker.com/api/agent/v1/node/
2016/12/21 16:54:31 The token is empty. Please run 'dockercloud-agent set Token=xxx' first!
2016/12/21 16:54:31 Running dockercloud-agent: version 1.1.0
2016/12/21 16:54:31 Create pid file(/var/run/dockercloud-agent.pid): 1689
2016/12/21 16:54:31 Checking if config file exists
2016/12/21 16:54:31 Loading Configuration file
2016/12/21 16:54:31 Registering in Docker Cloud via POST: https://cloud.docker.com/api/agent/v1/node/
2016/12/21 16:54:31 The token is empty. Please run 'dockercloud-agent set Token=xxx' first!
2016/12/21 16:54:32 Running dockercloud-agent: version 1.1.0
2016/12/21 16:54:32 Create pid file(/var/run/dockercloud-agent.pid): 1731
2016/12/21 16:54:32 Checking if config file exists
2016/12/21 16:54:32 Loading Configuration file
2016/12/21 16:54:32 Registering in Docker Cloud via POST: https://cloud.docker.com/api/agent/v1/node/
2016/12/21 16:54:32 The token is empty. Please run 'dockercloud-agent set Token=xxx' first!
2016/12/22 04:01:35 Running dockercloud-agent: version 1.1.0
2016/12/22 04:01:35 Create pid file(/var/run/dockercloud-agent.pid): 1163
2016/12/22 04:01:35 Checking if config file exists
2016/12/22 04:01:35 Loading Configuration file
2016/12/22 04:01:35 Registering in Docker Cloud via POST: https://cloud.docker.com/api/agent/v1/node/
2016/12/22 04:01:35 The token is empty. Please run 'dockercloud-agent set Token=xxx' first!
2016/12/22 04:01:36 Running dockercloud-agent: version 1.1.0
2016/12/22 04:01:36 Create pid file(/var/run/dockercloud-agent.pid): 1304
2016/12/22 04:01:36 Checking if config file exists
2016/12/22 04:01:36 Loading Configuration file
2016/12/22 04:01:36 Registering in Docker Cloud via POST: https://cloud.docker.com/api/agent/v1/node/
2016/12/22 04:01:36 The token is empty. Please run 'dockercloud-agent set Token=xxx' first!
2016/12/22 04:01:36 Running dockercloud-agent: version 1.1.0
2016/12/22 04:01:36 Create pid file(/var/run/dockercloud-agent.pid): 1398
2016/12/22 04:01:36 Checking if config file exists
2016/12/22 04:01:36 Loading Configuration file
2016/12/22 04:01:36 Registering in Docker Cloud via POST: https://cloud.docker.com/api/agent/v1/node/
2016/12/22 04:01:36 The token is empty. Please run 'dockercloud-agent set Token=xxx' first!
2016/12/22 04:01:37 Running dockercloud-agent: version 1.1.0
2016/12/22 04:01:37 Create pid file(/var/run/dockercloud-agent.pid): 1567
2016/12/22 04:01:37 Checking if config file exists
2016/12/22 04:01:37 Loading Configuration file
2016/12/22 04:01:37 Registering in Docker Cloud via POST: https://cloud.docker.com/api/agent/v1/node/
2016/12/22 04:01:37 The token is empty. Please run 'dockercloud-agent set Token=xxx' first!
2016/12/22 04:01:38 Running dockercloud-agent: version 1.1.0
2016/12/22 04:01:38 Create pid file(/var/run/dockercloud-agent.pid): 1651
2016/12/22 04:01:38 Checking if config file exists
2016/12/22 04:01:38 Loading Configuration file
2016/12/22 04:01:38 Registering in Docker Cloud via POST: https://cloud.docker.com/api/agent/v1/node/
2016/12/22 04:01:38 The token is empty. Please run 'dockercloud-agent set Token=xxx' first!
2016/12/22 04:01:38 Running dockercloud-agent: version 1.1.0
2016/12/22 04:01:38 Create pid file(/var/run/dockercloud-agent.pid): 1692
2016/12/22 04:01:38 Checking if config file exists
2016/12/22 04:01:38 Loading Configuration file
2016/12/22 04:01:38 Registering in Docker Cloud via POST: https://cloud.docker.com/api/agent/v1/node/
2016/12/22 04:01:38 The token is empty. Please run 'dockercloud-agent set Token=xxx' first!
2016/12/22 04:01:38 Running dockercloud-agent: version 1.1.0
2016/12/22 04:01:38 Create pid file(/var/run/dockercloud-agent.pid): 1735
2016/12/22 04:01:38 Checking if config file exists
2016/12/22 04:01:38 Loading Configuration file
2016/12/22 04:01:38 Registering in Docker Cloud via POST: https://cloud.docker.com/api/agent/v1/node/
2016/12/22 04:01:38 The token is empty. Please run 'dockercloud-agent set Token=xxx' first!
2016/12/22 12:30:58 Running dockercloud-agent: version 1.1.0
2016/12/22 12:30:58 Create pid file(/var/run/dockercloud-agent.pid): 3913
2016/12/22 12:30:58 Checking if config file exists
2016/12/22 12:30:58 Loading Configuration file
2016/12/22 12:30:58 Registering in Docker Cloud via POST: https://cloud.docker.com/api/agent/v1/node/
2016/12/22 12:30:58 The token is empty. Please run 'dockercloud-agent set Token=xxx' first!
2016/12/22 12:30:58 Running dockercloud-agent: version 1.1.0
2016/12/22 12:30:58 Create pid file(/var/run/dockercloud-agent.pid): 3953
2016/12/22 12:30:58 Checking if config file exists
2016/12/22 12:30:58 Loading Configuration file
2016/12/22 12:30:58 Registering in Docker Cloud via POST: https://cloud.docker.com/api/agent/v1/node/
2016/12/22 12:30:58 The token is empty. Please run 'dockercloud-agent set Token=xxx' first!
2016/12/22 12:30:58 Running dockercloud-agent: version 1.1.0
2016/12/22 12:30:58 Create pid file(/var/run/dockercloud-agent.pid): 3995
2016/12/22 12:30:58 Checking if config file exists
2016/12/22 12:30:58 Loading Configuration file
2016/12/22 12:30:58 Registering in Docker Cloud via POST: https://cloud.docker.com/api/agent/v1/node/
2016/12/22 12:30:58 The token is empty. Please run 'dockercloud-agent set Token=xxx' first!
2016/12/22 12:30:58 Running dockercloud-agent: version 1.1.0
2016/12/22 12:30:58 Create pid file(/var/run/dockercloud-agent.pid): 4036
2016/12/22 12:30:58 Checking if config file exists
2016/12/22 12:30:58 Loading Configuration file
2016/12/22 12:30:58 Registering in Docker Cloud via POST: https://cloud.docker.com/api/agent/v1/node/
2016/12/22 12:30:58 The token is empty. Please run 'dockercloud-agent set Token=xxx' first!

How can I recover these nodes? I appreciate your help.