{"action":"closed","issue":{"url":"https://api.github.com/repos/luxas/kubernetes-on-arm/issues/35","labels_url":"https://api.github.com/repos/luxas/kubernetes-on-arm/issues/35/labels{/name}","comments_url":"https://api.github.com/repos/luxas/kubernetes-on-arm/issues/35/comments","events_url":"https://api.github.com/repos/luxas/kubernetes-on-arm/issues/35/events","html_url":"https://github.com/luxas/kubernetes-on-arm/issues/35","id":124022227,"number":35,"title":"Install fails on kube-config enable-worker [master-ip] - using Arch + RPI2","user":{"login":"kyletravis","id":7444723,"avatar_url":"https://avatars.githubusercontent.com/u/7444723?v=3","gravatar_id":"","url":"https://api.github.com/users/kyletravis","html_url":"https://github.com/kyletravis","followers_url":"https://api.github.com/users/kyletravis/followers","following_url":"https://api.github.com/users/kyletravis/following{/other_user}","gists_url":"https://api.github.com/users/kyletravis/gists{/gist_id}","starred_url":"https://api.github.com/users/kyletravis/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kyletravis/subscriptions","organizations_url":"https://api.github.com/users/kyletravis/orgs","repos_url":"https://api.github.com/users/kyletravis/repos","events_url":"https://api.github.com/users/kyletravis/events{/privacy}","received_events_url":"https://api.github.com/users/kyletravis/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-12-28T05:49:55Z","updated_at":"2015-12-29T22:36:16Z","closed_at":"2015-12-29T22:36:16Z","body":"Hello, first off thanks for putting this together - it has provided a great learning experience over the holiday break after receiving a couple of RPI2's to tinker with! And a cheaper route than Google Cloud :+1: \r\n\r\nI encountered an issue when enabling the workers following a clean install of both the master and worker. It appears to be searching for 127.0.0.1 instead of the value based on the cli argument. This was run after the master came up successfully.\r\n\r\n```\r\nroot@kube-slave01 ~]# kube-config enable-worker 192.168.0.20\r\nDisabling k8s if it is running\r\nUsing master ip: 127.0.0.1\r\ncurl: (6) Could not resolve host: \r\nKubernetes Master IP is required.\r\nValue right now: 127.0.0.1\r\nExiting...\r\n\r\nCommand:\r\nkube-config enable-worker [master-ip]\r\nChecks so all images are present\r\nDownloading Kubernetes docker images from Github\r\nTransferring images to system-docker, if necessary\r\nCopying kubernetesonarm/flannel to system-docker\r\nCreated symlink from /etc/systemd/system/multi-user.target.wants/flannel.service to /usr/lib/systemd/system/flannel.service.\r\nJob for docker.service failed because a configured resource limit was exceeded. See \"systemctl status docker.service\" and \"journalctl -xe\" for details.\r\n```\r\n\r\nI was able to tweak the /usr/bin/kube-config file and achieve the expected behavior below. Stay tuned for a quick pull request.\r\n\r\n```\r\n[root@kube-slave02 ~]# kube-config enable-worker 192.168.0.20\r\nDisabling k8s if it is running\r\nUsing master ip: 192.168.0.20\r\nChecks so all images are present\r\nDownloading Kubernetes docker images from Github\r\nTransferring images to system-docker, if necessary\r\nCopying kubernetesonarm/flannel to system-docker\r\nCreated symlink from /etc/systemd/system/multi-user.target.wants/flannel.service to /usr/lib/systemd/system/flannel.service.\r\nStarting worker components in docker containers\r\nCreated symlink from /etc/systemd/system/multi-user.target.wants/k8s-worker.service to /usr/lib/systemd/system/k8s-worker.service.\r\nKubernetes worker services enabled\r\n```"}}