{"action":"created","issue":{"url":"https://api.github.com/repos/coreos/coreos-kubernetes/issues/801","repository_url":"https://api.github.com/repos/coreos/coreos-kubernetes","labels_url":"https://api.github.com/repos/coreos/coreos-kubernetes/issues/801/labels{/name}","comments_url":"https://api.github.com/repos/coreos/coreos-kubernetes/issues/801/comments","events_url":"https://api.github.com/repos/coreos/coreos-kubernetes/issues/801/events","html_url":"https://github.com/coreos/coreos-kubernetes/issues/801","id":199091264,"number":801,"title":"Calico + rkt Fails due to CNI error","user":{"login":"ElijahCaine","id":1897147,"avatar_url":"https://avatars.githubusercontent.com/u/1897147?v=3","gravatar_id":"","url":"https://api.github.com/users/ElijahCaine","html_url":"https://github.com/ElijahCaine","followers_url":"https://api.github.com/users/ElijahCaine/followers","following_url":"https://api.github.com/users/ElijahCaine/following{/other_user}","gists_url":"https://api.github.com/users/ElijahCaine/gists{/gist_id}","starred_url":"https://api.github.com/users/ElijahCaine/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ElijahCaine/subscriptions","organizations_url":"https://api.github.com/users/ElijahCaine/orgs","repos_url":"https://api.github.com/users/ElijahCaine/repos","events_url":"https://api.github.com/users/ElijahCaine/events{/privacy}","received_events_url":"https://api.github.com/users/ElijahCaine/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":14,"created_at":"2017-01-06T00:00:02Z","updated_at":"2017-01-25T17:49:25Z","closed_at":null,"body":"This was discussed in the `#kubernetes-users` channel on the K8s Slack but I wanted to make sure it was documented here.\r\n\r\n## TLDR\r\n\r\nWhen Calico + rkt are enabled on the vagrant (and other setups?) multi-node cluster all pods get stuck at the `CreatingContainer` phase because of some problem with CNI not begin setup.\r\n\r\n## Problem\r\n\r\nUsing the latest commit ( 79b7350fe2e45a1a5e9ed0f34a904eb10c158232 ), when `rkt` and `calico` are enabled, ( i.e.,\r\n```bash\r\n# Whether to use Calico for Kubernetes network policy.\r\nexport USE_CALICO=true\r\n\r\n# Determines the container runtime for kubernetes to use. Accepts 'docker' or 'rkt'.\r\nexport CONTAINER_RUNTIME=rkt\r\n```\r\nis set in `controller-install.sh` and `worker-install.sh` ) we get the following error when trying to create a Pod:\r\n\r\n```\r\n$ kubectl create -f <spec for deployment with busybox container pod>\r\n$ kubectl get pods\r\nNAME                         READY     STATUS              RESTARTS   AGE\r\napp-deploy-172403538-gvwpz   0/1       ContainerCreating   0          1m\r\n$ kubectl describe pod app-deploy-172403538-gvwpz\r\n[...]\r\nEvents:\r\n  FirstSeen\tLastSeen\tCount\tFrom\t\t\tSubObjectPath\tType\t\tReason\t\t\tMessage\r\n  ---------\t--------\t-----\t----\t\t\t-------------\t--------\t------\t\t\t-------\r\n  44s\t\t29s\t\t6\t{default-scheduler }\t\t\tWarning\t\tFailedScheduling\tno nodes available to schedule pods\r\n  12s\t\t12s\t\t1\t{default-scheduler }\t\t\tNormal\t\tScheduled\t\tSuccessfully assigned app-deploy-172403538-gvwpz to 172.17.4.202\r\n  12s\t\t1s\t\t2\t{kubelet 172.17.4.202}\t\t\tWarning\t\tFailedSync\t\tError syncing pod, skipping: failed to SyncPod: failed to set up pod network: cni config unintialized\r\n```\r\n\r\nNodes have possibly have a similar story:\r\n\r\n```\r\nkubectl describe node <node name>\r\n[...]\r\n OS Image:\t\t\tContainer Linux by CoreOS 1284.0.0 (Ladybug)\r\n[...]\r\n Container Runtime Version:\trkt://1.21.0\r\n Kubelet Version:\t\tv1.5.1+coreos.0\r\n Kube-Proxy Version:\t\tv1.5.1+coreos.0\r\n[...]\r\n  FirstSeen\tLastSeen\tCount\tFrom\t\t\tSubObjectPath\tType\t\tReason\t\t\tMessage\r\n  ---------\t--------\t-----\t----\t\t\t-------------\t--------\t------\t\t\t-------\r\n  5m\t\t5m\t\t1\t{kubelet 172.17.4.101}\t\t\tWarning\t\tImageGCFailed\t\tunable to find data for container /\r\n[... everything else normal ...]\r\n```\r\n\r\n## Specs\r\n\r\n```\r\n$ vagrant version\r\nInstalled Version: 1.8.6\r\nLatest Version: 1.9.1\r\n$ kubectl version\r\nClient Version: version.Info{Major:\"1\", Minor:\"5\", GitVersion:\"v1.5.1\", GitCommit:\"82450d03cb057bab0950214ef122b67c83fb11df\", GitTreeState:\"clean\", BuildDate:\"2016-12-14T00:57:05Z\", GoVersion:\"go1.7.4\", Compiler:\"gc\", Platform:\"darwin/amd64\"}\r\nServer Version: version.Info{Major:\"1\", Minor:\"5\", GitVersion:\"v1.5.1+coreos.0\", GitCommit:\"cc65f5321f9230bf9a3fa171155c1213d6e3480e\", GitTreeState:\"clean\", BuildDate:\"2016-12-14T04:08:28Z\", GoVersion:\"go1.7.4\", Compiler:\"gc\", Platform:\"linux/amd64\"}\r\n```\r\n\r\n## Hints\r\n\r\nIt was mentioned in channel that this is because of the Hyperkube image and it's compatibility with rkt [and/or] calico. I wasn't sure how to put that theory to the test so I can't confirm it."},"comment":{"url":"https://api.github.com/repos/coreos/coreos-kubernetes/issues/comments/275180368","html_url":"https://github.com/coreos/coreos-kubernetes/issues/801#issuecomment-275180368","issue_url":"https://api.github.com/repos/coreos/coreos-kubernetes/issues/801","id":275180368,"user":{"login":"Promaethius","id":677559,"avatar_url":"https://avatars.githubusercontent.com/u/677559?v=3","gravatar_id":"","url":"https://api.github.com/users/Promaethius","html_url":"https://github.com/Promaethius","followers_url":"https://api.github.com/users/Promaethius/followers","following_url":"https://api.github.com/users/Promaethius/following{/other_user}","gists_url":"https://api.github.com/users/Promaethius/gists{/gist_id}","starred_url":"https://api.github.com/users/Promaethius/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Promaethius/subscriptions","organizations_url":"https://api.github.com/users/Promaethius/orgs","repos_url":"https://api.github.com/users/Promaethius/repos","events_url":"https://api.github.com/users/Promaethius/events{/privacy}","received_events_url":"https://api.github.com/users/Promaethius/received_events","type":"User","site_admin":false},"created_at":"2017-01-25T17:49:25Z","updated_at":"2017-01-25T17:49:25Z","body":"@caseydavenport CNI doesn't need it but rkt has a section of global mounts passed into the service file with resolv.conf already specified. When rkt tried to mount it twice, it broke. This is why I removed that volume from the CNI, both because it doesn't need and and because it's already a global mount."}}
{"actor":{"display_login":"Promaethius"}}