Docker Community Forums

Share and learn in the Docker community.

BYON (Bring your own node) unable to register with docker cloud is this broken?


(Webengine) #1

Trying to add my own node to docker cloud - we’ve a dedicated server in the office we want to use.

Short version - upon following the instructions on configuring BYON instance we end up with -

Complete!
-> Configuring dockercloud-agent...
-> Enabling dockercloud-agent to start on boot on systemd...
-> Starting dockercloud-agent service...
Starting dockercloud-agent (via systemctl):                [  OK  ]
-> Done!

*******************************************************************************
Docker Cloud Agent installed successfully
*******************************************************************************

You can now deploy containers to this node using Docker Cloud

[root@znet ~]# service dockercloud-agent restart
Restarting dockercloud-agent (via systemctl):              [  OK  ]

This is CentOS 7, I’ve opened the ports on the firewall and forwarded them from the router from our external interface.

Docker cloud initially looks like it’s going to work, after some delay it terminates and it disappears from docker cloud.

Then trying to re-register the node by following the process again it tells me it’s already installed and to restart the service.

I restart the service, makes no difference.

Figuring it might need re-starting all over again, having checked firewall/forwards etc I removed the packages -

service dockercloud-agent stop
yum remove dockercloud-agent
rm -rf /etc/dockercloud

Then re-ran the script to hookup the node, but got the same. And like groundhog day - the same results every time.

Note - I’m aware of the ports to open - this was done as follows and the ports forwarded from the router to the server (both UDP and TCP) -

firewall-cmd --zone=public --add-port=21597/tcp --permanent
firewall-cmd --zone=public --add-port=21597/udp --permanent
firewall-cmd --zone=public --add-port=6783/tcp --permanent
firewall-cmd --zone=public --add-port=6783/udp --permanent
firewall-cmd --reload

For brevity here are my detailed steps in long hand -

Hit the BYON option - get the curl command and told -
Waiting for contact from agent


curl -Ls https://get.cloud.docker.com/ | sudo -H sh -s 08789axxxxxxxxxxxxxx

-> Adding Docker Cloud's GPG key...
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: anorien.csc.warwick.ac.uk
 * extras: anorien.csc.warwick.ac.uk
 * updates: mirror.mhd.uk.as44574.net
Package gnupg2-2.0.22-4.el7.x86_64 already installed and latest version
Package rpm-4.11.3-25.el7.x86_64 already installed and latest version
Package curl-7.29.0-42.el7.x86_64 already installed and latest version
Nothing to do
gpg: key EF170D1C: "Tutum Inc. (tutum) " not changed
gpg: Total number processed: 1
gpg:              unchanged: 1
-> Installing dockercloud-agent...
Loaded plugins: fastestmirror
dockercloud/x86_64/signature                                                                                                                                                                   |  473 B  00:00:00
dockercloud/x86_64/signature                                                                                                                                                                   | 2.9 kB  00:00:00 !!!
Loading mirror speeds from cached hostfile
 * base: mirror.netw.io
 * extras: anorien.csc.warwick.ac.uk
 * updates: mirror.mhd.uk.as44574.net
Resolving Dependencies
--> Running transaction check
---> Package dockercloud-agent.x86_64 0:1.1.0-1 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

Installing:
 dockercloud-agent                                         x86_64                                         1.1.0-1                                           dockercloud                                         2.6 M

Transaction Summary

Install  1 Package

Total download size: 2.6 M
Installed size: 8.9 M
Downloading packages:
dockercloud-agent-1.1.0-1.x86_64.rpm                                                                                                                                                           | 2.6 MB  00:00:02
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
  Installing : dockercloud-agent-1.1.0-1.x86_64                                                                                                                                                                   1/1
Usage: /etc/init.d/dockercloud-agent {start|stop|status|restart|condrestart|try-restart|reload|force-reload}
  Verifying  : dockercloud-agent-1.1.0-1.x86_64                                                                                                                                                                   1/1

Installed:
  dockercloud-agent.x86_64 0:1.1.0-1

Complete!
-> Configuring dockercloud-agent...
-> Enabling dockercloud-agent to start on boot on systemd...
-> Starting dockercloud-agent service...
Starting dockercloud-agent (via systemctl):                [  OK  ]
-> Done!

*******************************************************************************
Docker Cloud Agent installed successfully
*******************************************************************************

You can now deploy containers to this node using Docker Cloud

Now cloud.docker is reporting -
Contacting Daemon

In the popover…

This is as far as it appears to get - if I refresh the page says DEPLOYING against the node in the list. About 15 mins later this will eventually shows Error creating node and is listed as terminated.

Contents of the log as follows -

[root@znet ~]# tail -f /var/log/dockercloud/agent.log
2017/11/23 12:43:46 Cert CommonName has been changed from  to ad9c1340-xxxxxxxxxx.node.dockerapp.io
2017/11/23 12:43:46 UUID has been changed from  to ad9c1340-xxxxxxxxxx
2017/11/23 12:43:46 Updating configuration file...
2017/11/23 12:43:46 New TLS certificates generated
2017/11/23 12:43:46 Registering in Docker Cloud via PATCH: https://cloud.docker.com/api/agent/v1/node/ad9c1340-xxxxxxxxxx

In fact looking at dockercloud we can see this UUID listed against the machine that ultimately terminates.

Is this even working? Can’t find any clear answers anywhere on this?


(Laurent Kempé) #2

I have exactly the same issue, could you solve it?


(Webengine) #3

Nope - given up on docker for now to focus on our KVM stack, but will be looking at this again in a few months time. Feel like this might underline docker want you to use their cloud rather than your own cloud for provisioning and BYON cuts against the commercial model, happy to be proven wrong.


(Laurent Kempé) #4

Yeah not sure what’s going on there, it was working good at first trial but now after several trial it doesn’t work, too bad


(Stefanosirplay) #5

I have the same problem.