{"action":"created","issue":{"url":"https://api.github.com/repos/Shippable/support/issues/1196","labels_url":"https://api.github.com/repos/Shippable/support/issues/1196/labels{/name}","comments_url":"https://api.github.com/repos/Shippable/support/issues/1196/comments","events_url":"https://api.github.com/repos/Shippable/support/issues/1196/events","html_url":"https://github.com/Shippable/support/issues/1196","id":63398897,"number":1196,"title":"connection error on dedicated node","user":{"login":"fommil","id":1914041,"avatar_url":"https://avatars.githubusercontent.com/u/1914041?v=3","gravatar_id":"","url":"https://api.github.com/users/fommil","html_url":"https://github.com/fommil","followers_url":"https://api.github.com/users/fommil/followers","following_url":"https://api.github.com/users/fommil/following{/other_user}","gists_url":"https://api.github.com/users/fommil/gists{/gist_id}","starred_url":"https://api.github.com/users/fommil/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fommil/subscriptions","organizations_url":"https://api.github.com/users/fommil/orgs","repos_url":"https://api.github.com/users/fommil/repos","events_url":"https://api.github.com/users/fommil/events{/privacy}","received_events_url":"https://api.github.com/users/fommil/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-03-21T12:21:59Z","updated_at":"2015-03-21T13:08:45Z","closed_at":"2015-03-21T13:08:45Z","body":"I have two dedicated nodes: both successfully deployed, but one is working and the other is not. Both are hosted by the same provider, but are running different flavours of Linux: the succeeding one is running Ubuntu, the failing one is running Debian.\r\n\r\nThis is an example of a failure https://app.shippable.com/builds/550d5d8f21d6a90b00366cf4 which is using the normal shippable docker image. It also fails for custom images.\r\n\r\n```\r\n Docker login\r\nWarning: Docker login failed for user fommil with error HTTPConnectionPool(host='127.0.0.1', port=4243): Max retries exceeded with url: /v1.15/auth (Caused by <class 'socket.error'>: [Errno 111] Connection refused)\r\n Docker pull shippable/minv2:latest\r\nHTTPConnectionPool(host='127.0.0.1', port=4243): Max retries exceeded with url: /v1.15/images/create?tag=latest&fromImage=shippable%2Fminv2 (Caused by <class 'socket.error'>: [Errno 111] Connection refused): Traceback (most recent call last):\r\n  File \"/home/shippable/dpd/step_listener.py\", line 99, in handle_message_callback\r\n    self.execute_step(build_plan, current_step, False)\r\n  File \"/home/shippable/dpd/step_listener.py\", line 165, in execute_step\r\n    raise e\r\nConnectionError: HTTPConnectionPool(host='127.0.0.1', port=4243): Max retries exceeded with url: /v1.15/images/create?tag=latest&fromImage=shippable%2Fminv2 (Caused by <class 'socket.error'>: [Errno 111] Connection refused)\r\n```\r\n\r\nIf I manually log in to the box as the `shippable` user, I am able to issue this command\r\n\r\n```\r\ndocker pull shippable/minv2 \r\n```\r\n\r\nwhich works (although, notably, it had to download everything first).\r\n\r\nIt would help me greatly if you could let me see the script that is running and failing... there is probably some missing unix utility or a python/shell version mismatch."},"comment":{"url":"https://api.github.com/repos/Shippable/support/issues/comments/84332739","html_url":"https://github.com/Shippable/support/issues/1196#issuecomment-84332739","issue_url":"https://api.github.com/repos/Shippable/support/issues/1196","id":84332739,"user":{"login":"fommil","id":1914041,"avatar_url":"https://avatars.githubusercontent.com/u/1914041?v=3","gravatar_id":"","url":"https://api.github.com/users/fommil","html_url":"https://github.com/fommil","followers_url":"https://api.github.com/users/fommil/followers","following_url":"https://api.github.com/users/fommil/following{/other_user}","gists_url":"https://api.github.com/users/fommil/gists{/gist_id}","starred_url":"https://api.github.com/users/fommil/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fommil/subscriptions","organizations_url":"https://api.github.com/users/fommil/orgs","repos_url":"https://api.github.com/users/fommil/repos","events_url":"https://api.github.com/users/fommil/events{/privacy}","received_events_url":"https://api.github.com/users/fommil/received_events","type":"User","site_admin":false},"created_at":"2015-03-21T13:08:45Z","updated_at":"2015-03-21T13:08:45Z","body":"w00t! Got it. You are assuming that the host is running the docker API on port 4243. This is definitely not a universal assumption. The workaround is to enable the service on localhost, e.g. in debian this means adding to `/etc/default/docker` the following\r\n\r\n```\r\nDOCKER_OPTS='-H tcp://127.0.0.1:4243 -H unix:///var/run/docker.sock'\r\n```\r\n\r\nHowever, I would **strongly** recommend that you only use the unix socks mechanism (docker default), because a) it is a lot more secure and b) you already require unix socks support when initialising the node.\r\n"}}