{"action":"created","issue":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/24588","repository_url":"https://api.github.com/repos/kubernetes/kubernetes","labels_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/24588/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/24588/comments","events_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/24588/events","html_url":"https://github.com/kubernetes/kubernetes/issues/24588","id":149980188,"number":24588,"title":"Unable to launch container, error complaining about SHM size must be greater than 0","user":{"login":"derekwaynecarr","id":6233452,"avatar_url":"https://avatars.githubusercontent.com/u/6233452?v=3","gravatar_id":"","url":"https://api.github.com/users/derekwaynecarr","html_url":"https://github.com/derekwaynecarr","followers_url":"https://api.github.com/users/derekwaynecarr/followers","following_url":"https://api.github.com/users/derekwaynecarr/following{/other_user}","gists_url":"https://api.github.com/users/derekwaynecarr/gists{/gist_id}","starred_url":"https://api.github.com/users/derekwaynecarr/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/derekwaynecarr/subscriptions","organizations_url":"https://api.github.com/users/derekwaynecarr/orgs","repos_url":"https://api.github.com/users/derekwaynecarr/repos","events_url":"https://api.github.com/users/derekwaynecarr/events{/privacy}","received_events_url":"https://api.github.com/users/derekwaynecarr/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/kubernetes/kubernetes/labels/priority/P0","name":"priority/P0","color":"e11d21"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2016-04-21T06:31:31Z","updated_at":"2016-04-21T08:04:14Z","closed_at":null,"body":"I am getting errors like the following:\r\n\r\n```\r\n$ cluster/kubectl.sh describe pods\r\nName:\t\tnginx-2040093540-0ietl\r\nNamespace:\tdefault\r\nNode:\t\t127.0.0.1/127.0.0.1\r\nStart Time:\tThu, 21 Apr 2016 02:10:40 -0400\r\nLabels:\t\tpod-template-hash=2040093540,run=nginx\r\nStatus:\t\tPending\r\nIP:\t\t\r\nControllers:\tReplicaSet/nginx-2040093540\r\nContainers:\r\n  nginx:\r\n    Container ID:\t\r\n    Image:\t\tnginx\r\n    Image ID:\t\t\r\n    Port:\t\t\r\n    QoS Tier:\r\n      cpu:\t\t\tBestEffort\r\n      memory:\t\t\tBestEffort\r\n    State:\t\t\tWaiting\r\n      Reason:\t\t\tContainerCreating\r\n    Ready:\t\t\tFalse\r\n    Restart Count:\t\t0\r\n    Environment Variables:\t<none>\r\nConditions:\r\n  Type\t\tStatus\r\n  Ready \tFalse \r\nVolumes:\r\n  default-token-h7ms3:\r\n    Type:\tSecret (a volume populated by a Secret)\r\n    SecretName:\tdefault-token-h7ms3\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  48s\t\t48s\t\t1\t{default-scheduler }\t\t\tWarning\t\tFailedScheduling\tno nodes available to schedule pods\r\n  47s\t\t47s\t\t1\t{default-scheduler }\t\t\tNormal\t\tScheduled\t\tSuccessfully assigned nginx-2040093540-0ietl to 127.0.0.1\r\n  44s\t\t8s\t\t4\t{kubelet 127.0.0.1}\t\t\tWarning\t\tFailedSync\t\tError syncing pod, skipping: failed to \"StartContainer\" for \"POD\" with RunContainerError: \"runContainer: Error response from daemon: SHM size must be greater then 0\"\r\n```\r\n\r\nI am running the following:\r\n\r\n```\r\n$ uname -r\r\n4.4.7-300.fc23.x86_64$ \r\n$ docker version\r\nClient:\r\n Version:         1.9.1\r\n API version:     1.21\r\n Package version: docker-1.9.1-9.gitee06d03.fc23.x86_64\r\n Go version:      go1.5.3\r\n Git commit:      ee06d03/1.9.1\r\n Built:           \r\n OS/Arch:         linux/amd64\r\n\r\nServer:\r\n Version:         1.9.1\r\n API version:     1.21\r\n Package version: docker-1.9.1-9.gitee06d03.fc23.x86_64\r\n Go version:      go1.5.3\r\n Git commit:      ee06d03/1.9.1\r\n Built:           \r\n OS/Arch:         linux/amd64\r\n```\r\n\r\nAre we now required to set a `ShmSize` moving forward now that we have switched to the docker engine API?  I was able to work around it on my system by supplying `ShmSize` like the following:\r\n\r\n```\r\n\thc := &dockercontainer.HostConfig{\r\n\t\tBinds:          binds,\r\n\t\tNetworkMode:    dockercontainer.NetworkMode(netMode),\r\n\t\tIpcMode:        dockercontainer.IpcMode(ipcMode),\r\n\t\tUTSMode:        dockercontainer.UTSMode(utsMode),\r\n\t\tPidMode:        dockercontainer.PidMode(pidMode),\r\n\t\tReadonlyRootfs: readOnlyRootFilesystem(container),\r\n\t\tResources: dockercontainer.Resources{\r\n\t\t\tMemory:     memoryLimit,\r\n\t\t\tMemorySwap: -1,\r\n\t\t\tCPUShares:  cpuShares,\r\n\t\t},\r\n\t\tShmSize:     1024 * 1024 * 64,\r\n\t\tSecurityOpt: securityOpts,\r\n\t}\r\n```\r\n\r\nwhich I think is consistent with what docker CLI is doing by default.\r\n\r\n/cc @kubernetes/sig-node @vishh @Random-Liu @mrunalp @kubernetes/rh-cluster-infra "},"comment":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/comments/212795592","html_url":"https://github.com/kubernetes/kubernetes/issues/24588#issuecomment-212795592","issue_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/24588","id":212795592,"user":{"login":"Random-Liu","id":5821883,"avatar_url":"https://avatars.githubusercontent.com/u/5821883?v=3","gravatar_id":"","url":"https://api.github.com/users/Random-Liu","html_url":"https://github.com/Random-Liu","followers_url":"https://api.github.com/users/Random-Liu/followers","following_url":"https://api.github.com/users/Random-Liu/following{/other_user}","gists_url":"https://api.github.com/users/Random-Liu/gists{/gist_id}","starred_url":"https://api.github.com/users/Random-Liu/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Random-Liu/subscriptions","organizations_url":"https://api.github.com/users/Random-Liu/orgs","repos_url":"https://api.github.com/users/Random-Liu/repos","events_url":"https://api.github.com/users/Random-Liu/events{/privacy}","received_events_url":"https://api.github.com/users/Random-Liu/received_events","type":"User","site_admin":false},"created_at":"2016-04-21T08:04:14Z","updated_at":"2016-04-21T08:04:14Z","body":"@derekwaynecarr \r\nIn our ContainerVM, we are using the earliest docker 1.9.1:\r\nhttps://github.com/docker/docker/commit/a34a1d5\r\n\r\nWhile the `ShmSize` PR gets in after that:\r\nhttps://github.com/docker/docker/pull/16168\r\n\r\nThe version you are using quite new:\r\nhttps://github.com/docker/docker/commit/ee06d03\r\n\r\nWhen I validated docker 1.10, we were still using go-dockerclient, which doesn't have this problem (see https://github.com/kubernetes/kubernetes/issues/24588#issuecomment-212784346)."}}