{"action":"created","issue":{"url":"https://api.github.com/repos/docker/docker/issues/22818","repository_url":"https://api.github.com/repos/docker/docker","labels_url":"https://api.github.com/repos/docker/docker/issues/22818/labels{/name}","comments_url":"https://api.github.com/repos/docker/docker/issues/22818/comments","events_url":"https://api.github.com/repos/docker/docker/issues/22818/events","html_url":"https://github.com/docker/docker/issues/22818","id":155563733,"number":22818,"title":"System error: The minimum allowed cpu-shares is 1024","user":{"login":"davidewatson","id":11819015,"avatar_url":"https://avatars.githubusercontent.com/u/11819015?v=3","gravatar_id":"","url":"https://api.github.com/users/davidewatson","html_url":"https://github.com/davidewatson","followers_url":"https://api.github.com/users/davidewatson/followers","following_url":"https://api.github.com/users/davidewatson/following{/other_user}","gists_url":"https://api.github.com/users/davidewatson/gists{/gist_id}","starred_url":"https://api.github.com/users/davidewatson/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/davidewatson/subscriptions","organizations_url":"https://api.github.com/users/davidewatson/orgs","repos_url":"https://api.github.com/users/davidewatson/repos","events_url":"https://api.github.com/users/davidewatson/events{/privacy}","received_events_url":"https://api.github.com/users/davidewatson/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/docker/docker/labels/version/1.10","name":"version/1.10","color":"ededed"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-05-18T17:56:08Z","updated_at":"2016-05-18T19:56:38Z","closed_at":null,"body":"\r\nI have a 10-node kubernetes cluster running on AWS m3.medium instances with CoreOS. When I run the kubernetes density e2e tests, containers fail to start with the error \"System error: The minimum allowed cpu-shares is 1024\". The requested CPU shares is 10 for each container. I have not seen this error when using AWS m3.large instances.\r\n\r\n**Output of `docker version`:**\r\n\r\n```\r\ncore@autoscaled ~ $ docker version\r\nClient:\r\n Version:      1.10.3\r\n API version:  1.22\r\n Go version:   go1.5.3\r\n Git commit:   8acee1b\r\n Built:        \r\n OS/Arch:      linux/amd64\r\n\r\nServer:\r\n Version:      1.10.3\r\n API version:  1.22\r\n Go version:   go1.5.3\r\n Git commit:   8acee1b\r\n Built:        \r\n OS/Arch:      linux/amd64\r\ncore@autoscaled ~ $\r\n```\r\n\r\n\r\n**Output of `docker info`:**\r\n\r\n```\r\ncore@autoscaled ~ $ docker info\r\nContainers: 2\r\n Running: 1\r\n Paused: 0\r\n Stopped: 1\r\nImages: 2\r\nServer Version: 1.10.3\r\nStorage Driver: overlay\r\n Backing Filesystem: extfs\r\nExecution Driver: native-0.2\r\nLogging Driver: json-file\r\nPlugins: \r\n Volume: local\r\n Network: null host bridge\r\nKernel Version: 4.5.0-coreos-r1\r\nOperating System: CoreOS 1010.1.0 (MoreOS)\r\nOSType: linux\r\nArchitecture: x86_64\r\nCPUs: 1\r\nTotal Memory: 3.679 GiB\r\nName: autoscaled\r\nID: R6H5:DVUQ:XSAD:K6RP:LQA2:MWXO:NUD2:UEP4:TNN6:Q3MN:3P66:BTSL\r\ncore@autoscaled ~ $\r\n```\r\n\r\n**Additional environment details (AWS, VirtualBox, physical, etc.):**\r\n\r\nThe non control plane nodes are m3.mediums (1 vCPU and 3.75 GiB RAM) running CoreOS version 1010.1.0 with docker 1.10, however I have also seen the error at least once using CoreOS 991.2.0 with docker 1.09.\r\n\r\n**Steps to reproduce the issue:**\r\n1. Create a kubernetes cluster with m3.medium nodes. My cluster was created using kraken with the following terraform configuration:\r\n\r\n```\r\naws_user_prefix = \"dew\"\r\nnode_count = \"10\"\r\naws_node_type = \"m3.medium\"\r\naws_etcd_type = \"m4.2xlarge\"\r\naws_master_type = \"m4.4xlarge\"\r\napiserver_count = \"1\"\r\naws_apiserver_type = \"m4.2xlarge\"\r\nspecial_node_type = \"m3.xlarge\"\r\ncoreos_update_channel = \"alpha\"\r\ncoreos_version = \"1010.1.0\"\r\n```\r\n\r\n2. Run the e2e density test.\r\n\r\n**Describe the results you received:**\r\n\r\n```\r\ncore@autoscaled ~ $ journalctl | grep cpu-shares\r\nMay 16 19:38:16 autoscaled dockerd[1083]: time=\"2016-05-16T19:38:16.992403355Z\" level=error msg=\"Handler for POST /containers/f7cbef37f15fb830c5b71934ff3e410f81605bbd4a85124cf6d0aaaa95214008/start returned error: Cannot start container f7cbef37f15fb830c5b71934ff3e410f81605bbd4a85124cf6d0aaaa95214008: [9] System error: The minimum allowed cpu-shares is 1024\"\r\nMay 16 19:38:16 autoscaled hyperkube[3827]: E0516 19:38:16.993365    3827 manager.go:1953] Error running pod \"density30-bbaecf52-1b9d-11e6-978f-f45c898cf22b-es0fh_e2e-tests-density-mmkq0(bba4d015-1b9d-11e6-86f1-02580e2da74b)\" container \"density30-bbaecf52-1b9d-11e6-978f-f45c898cf22b\": runContainer: API error (500): Cannot start container f7cbef37f15fb830c5b71934ff3e410f81605bbd4a85124cf6d0aaaa95214008: [9] System error: The minimum allowed cpu-shares is 1024\r\nMay 16 19:38:16 autoscaled hyperkube[3827]: E0516 19:38:16.993739    3827 pod_workers.go:138] Error syncing pod bba4d015-1b9d-11e6-86f1-02580e2da74b, skipping: failed to \"StartContainer\" for \"density30-bbaecf52-1b9d-11e6-978f-f45c898cf22b\" with RunContainerError: \"runContainer: API error (500): Cannot start container f7cbef37f15fb830c5b71934ff3e410f81605bbd4a85124cf6d0aaaa95214008: [9] System error: The minimum allowed cpu-shares is 1024\\n\"\r\ncore@autoscaled ~ $\r\n```\r\n\r\n**Describe the results you expected:**\r\n\r\nI expect the container to start.\r\n\r\n**Additional information you deem important (e.g. issue happens only occasionally):**\r\n\r\nI can reliably reproduce this on a 10 node cluster."},"comment":{"url":"https://api.github.com/repos/docker/docker/issues/comments/220139684","html_url":"https://github.com/docker/docker/issues/22818#issuecomment-220139684","issue_url":"https://api.github.com/repos/docker/docker/issues/22818","id":220139684,"user":{"login":"thaJeztah","id":1804568,"avatar_url":"https://avatars.githubusercontent.com/u/1804568?v=3","gravatar_id":"","url":"https://api.github.com/users/thaJeztah","html_url":"https://github.com/thaJeztah","followers_url":"https://api.github.com/users/thaJeztah/followers","following_url":"https://api.github.com/users/thaJeztah/following{/other_user}","gists_url":"https://api.github.com/users/thaJeztah/gists{/gist_id}","starred_url":"https://api.github.com/users/thaJeztah/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/thaJeztah/subscriptions","organizations_url":"https://api.github.com/users/thaJeztah/orgs","repos_url":"https://api.github.com/users/thaJeztah/repos","events_url":"https://api.github.com/users/thaJeztah/events{/privacy}","received_events_url":"https://api.github.com/users/thaJeztah/received_events","type":"User","site_admin":false},"created_at":"2016-05-18T19:56:38Z","updated_at":"2016-05-18T19:56:38Z","body":"This was fixed in libcontainer/runC (https://github.com/opencontainers/runc/pull/491), and should be fixed in docker 1.11, however, I think kubenetes is not yet working on docker 1.11"}}