search

docker-archive / dockercloud-agent

Agent to manage docker in nodes controlled by Docker Cloud
https://cloud.docker.com/
Apache License 2.0
34 stars 21 forks source link

Can not register node. #16

Open lexrus opened 8 years ago

lexrus commented 8 years ago

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
tifayuki commented 8 years ago

@lexrus The standalone mode is only used for us to run tests, and it assumes /usr/bin/docker exist.

Can you try to deploy a new node and paste the logs(/var/log/dockercloud/agent.log) if you still have the problem?

maietta commented 8 years ago

I have the same issue.

2016/06/30 10:28:28 Running dockercloud-agent: version 1.1.0 2016/06/30 10:28:28 Create pid file(/var/run/dockercloud-agent.pid): 2113 2016/06/30 10:28:28 Checking if config file exists 2016/06/30 10:28:28 Loading Configuration file 2016/06/30 10:28:28 Registering in Docker Cloud via POST: https://cloud.docker.com/api/agent/v1/node/ 2016/06/30 10:28:30 Registration failed, 402. Retry in 1 seconds 2016/06/30 10:28:32 Registration failed, 402. Retry in 2 seconds 2016/06/30 10:28:35 Registration failed, 402. Retry in 4 seconds 2016/06/30 10:28:40 Registration failed, 402. Retry in 8 seconds 2016/06/30 10:28:46 Running dockercloud-agent: version 1.1.0 2016/06/30 10:28:46 Found pid file, make sure that dockercloud-agent is not running or remove /var/run/dockercloud-agent.pid 2016/06/30 10:28:49 Registration failed, 402. Retry in 16 seconds 2016/06/30 10:28:53 Running dockercloud-agent: version 1.1.0 2016/06/30 10:28:53 Found pid file, make sure that dockercloud-agent is not running or remove /var/run/dockercloud-agent.pid 2016/06/30 10:29:06 Registration failed, 402. Retry in 32 seconds 2016/06/30 10:29:39 Registration failed, 402. Retry in 64 seconds 2016/06/30 10:47:36 Running dockercloud-agent: version 1.1.0 2016/06/30 10:47:36 Create pid file(/var/run/dockercloud-agent.pid): 10052 2016/06/30 10:47:36 Checking if config file exists 2016/06/30 10:47:36 Loading Configuration file 2016/06/30 10:47:36 Registering in Docker Cloud via POST: https://cloud.docker.com/api/agent/v1/node/ 2016/06/30 10:47:37 Registration failed, 402. Retry in 1 seconds 2016/06/30 10:47:39 Registration failed, 402. Retry in 2 seconds 2016/06/30 10:47:42 Registration failed, 402. Retry in 4 seconds 2016/06/30 10:47:48 Registration failed, 402. Retry in 8 seconds 2016/06/30 10:47:57 Registration failed, 402. Retry in 16 seconds 2016/06/30 10:48:14 Registration failed, 402. Retry in 32 seconds 2016/06/30 10:48:47 Registration failed, 402. Retry in 64 seconds 2016/06/30 10:49:05 Running dockercloud-agent: version 1.1.0 2016/06/30 10:49:05 Create pid file(/var/run/dockercloud-agent.pid): 10105 2016/06/30 10:49:05 Checking if config file exists 2016/06/30 10:49:05 Loading Configuration file 2016/06/30 10:49:05 Registering in Docker Cloud via POST: https://cloud.docker.com/api/agent/v1/node/ 2016/06/30 10:49:07 Registration failed, 402. Retry in 1 seconds 2016/06/30 10:49:10 Registration failed, 402. Retry in 2 seconds 2016/06/30 10:49:14 Registration failed, 402. Retry in 4 seconds 2016/06/30 10:49:19 Registration failed, 402. Retry in 8 seconds 2016/06/30 10:49:28 Registration failed, 402. Retry in 16 seconds

But then .. nothing ... after another 15 minutes.

I have been TRYING to find a way to completely start over. I am using a FRESH INSTALL of Ubuntu Server 15.04 LTS. No firewalls on a static IP. I am. Do we need to be editing documents to show what is required ahead of time? I mean, i've tried so many different ways to install docker, including docker.io, docker-machine, docker-engine... i just don't understand at this point why so many people have this problem yet nothing seems to be documented.

I have only been successful in registering a node in docker-cloud but on Ubuntu Service 16.04 LTS, but only after a bunch of different methods. I actually installed "experimental" release of docker only to have Docker-agent install and remove it and drop in another version of docker. The sad part was that after attempting to add the -g /data portion to my DOCKER_OPTS in /etc/defaults/docker, the service completely failed and never could be resurrected again.

tifayuki commented 8 years ago

@maietta 402 Payment Required which means you can only provision one free node without setting the billing info. If you need to configure more nodes, you need to go to the Web UI and complete the your billing info.

Thank you

dustinaevans commented 6 years ago

How bout this one?

level=fatal msg="Error starting daemon: Error initializing network controller: Error creating default \"bridge\" network: cannot create network a0da6cba6b2784b4f2a052e2d40bca575e618930c56529ca3c84d40d3f9ff43a (docker0): conflicts with network 4d4f3644718e5a1c4c66e7b4f5734229e0986df7eb50fec33a7b44efcadf2966 (docker0): networks have same bridge name

tifayuki commented 6 years ago

@dustinaevans The error is like the network is created by another docker engine. And the docker daemon managed by dockercloud-agent cannot run correctly.

The installation script doesn't work on the new version of linux distribution. It cannot remove the pre-installed docker packages correctly. That could be reason to have this kind of error.

dustinaevans commented 6 years ago

Thanks for your help. I corrected the issue with apt purge docker* and reinstalling the cloud agent.