Description of problem: Kubernetes master (commit 391ff9d) is unable to create containers with docker-1.9.1-9 Version-Release number of selected component (if applicable): docker-1.9.1-9.gitee06d03.fc23.x86_64 How reproducible: 100% Steps to Reproduce: 1. git clone https://github.com/kubernetes/kubernetes to $GOPATH/src/k8s.io/kubernetes 2. cd $GOPATH/src/k8s.io/kubernetes 3. sudo ./hack/local-up-cluster.sh 4. kubectl create -f docs/user-guide/pod.yaml 5. kubectl describe pod/nginx Actual results: Error syncing pod, skipping: failed to "StartContainer" for "POD" with RunContainerError: "runContainer: Error response from daemon: SHM size must be greater then 0" Expected results: Pod runs Additional info: Kubernetes has switched from go-dockerclient to docker's engine-api. As part of this change, the HostConfig's ShmSize is an int64, which means it gets defaulted to 0. go-dockerclient didn't contain this field, so it wasn't getting set. But now that it is defaulted to 0, when combined with https://github.com/projectatomic/docker/blob/fedora-1.9/daemon/daemon_unix.go#L138, you get the error listed above. It looks like docker 1.10 shouldn't have this problem: https://github.com/projectatomic/docker/blob/fedora-1.10/daemon/daemon_unix.go#L402. Would it be possible to either get an updated 1.9 or to have 1.10 in Fedora 23?
The change in our projectatomic/docker is a backport from 1.10 - 1.10 changed a bit from 1.9 and that check has been removed. I'm sure it's an error if you provide a negative shmSize, not sure if upstream is a bug or not. Can you actually create this pod if you use 1.10? shmSize should be validated in both 1.9 and 1.10 when is < 0
I will test with 1.10 on rawhide later tonight and report back. However, this pod creates a container that does not have ShmSize set... It's not that Kube is setting it to 0 and we can just fix Kube. We need to figure out how to make sure this will work in Docker instead of it being a validation error.
Found the patch and the login behind the change in 1.10 - will fix this for 1.9. It would be good if you could still test this in 1.10. Thanks!
1.10 on rawhide works fine
https://github.com/projectatomic/docker/pull/98
just tested and seems to be working now: 19:40:29 amurdaca at localhost in src/k8s.io/kubernetes ‹master*› cluster/kubectl.sh describe pod/nginx Name: nginx Namespace: default Node: 127.0.0.1/127.0.0.1 Start Time: Tue, 12 Apr 2016 19:37:18 +0200 Labels: app=nginx Status: Running IP: 172.17.0.2 Controllers: <none> Containers: nginx: Container ID: docker://dfea384c58a8ca44e72607cb947bfa181abab47bbeffc368e07fcb85c63d6b28 Image: nginx Image ID: docker://e32087da8ee6dfa45221c48670fa9475f3d8a53a0e9ccabef4f741c62c77d49b Port: 80/TCP QoS Tier: cpu: BestEffort memory: BestEffort State: Running Started: Tue, 12 Apr 2016 19:40:22 +0200 Ready: True Restart Count: 0 Environment Variables: <none> Conditions: Type Status Ready True Volumes: default-token-rye32: Type: Secret (a volume populated by a Secret) SecretName: default-token-rye32 Events: FirstSeen LastSeen Count From SubobjectPath Type Reason Message --------- -------- ----- ---- ------------- -------- ------ ------- 3m 3m 1 {default-scheduler } Normal Scheduled Successfully assigned nginx to 127.0.0.1 3m 3m 1 {kubelet 127.0.0.1} spec.containers{nginx} Normal Pulling pulling image "nginx" 9s 9s 1 {kubelet 127.0.0.1} spec.containers{nginx} Normal Pulled Successfully pulled image "nginx" 9s 9s 1 {kubelet 127.0.0.1} spec.containers{nginx} Normal Created Created container with docker id dfea384c58a8 8s 8s 1 {kubelet 127.0.0.1} spec.containers{nginx} Normal Started Started container with docker id dfea384c58a8
tested also the old 1.9 which showed me the error you are reporting. So this fix is working fine now.
Antonio which version of docker package is this fixed in?
docker-1.9 in rhel7-1.9 branch -> https://github.com/projectatomic/docker/pull/98 I didn't make a PR against fedora-1.9 branch because we don't seem to be shipping fixes for fedora anymore.
We need something in Fedora 23 that isn't broken.
confirmed this is working fine with docker-1.10.3
docker-1.10.3 is available for f23, I believe. Just in updates-testing, because we have been asked not to release it.
It's not there yet
Well it has been pulled back so that we can update the docker-1.9 version. I will ping lokesh to see if we can get it back into testing.
Fixed in docker-1.10.3 which is in updates-testing
docker-1.10.3-15.git964eda6.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-b59d274e19
docker-1.10.3-16.gita41254f.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-87f810b0f5
docker-1.10.3-16.gita41254f.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-87f810b0f5
docker-1.10.3-17.gitbba2d6d.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-c7e793ee33
docker-1.10.3-18.git667d6d1.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-7a1fb10a39
docker-1.10.3-18.git667d6d1.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-7a1fb10a39
docker-1.10.3-19.git8ecd47f.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-dd133dc2e9
docker-1.10.3-19.git8ecd47f.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-dd133dc2e9
docker-1.10.3-20.git8ecd47f.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-373d4f6308
so are we actually going to release 1.10 to fedora 23 now?
Created attachment 1161562 [details] Seeing this issue with Atomic App on Fedora as well
We will if k8s/OpenShift says we can.
docker-1.10.3-20.git8ecd47f.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-373d4f6308
docker-1.10.3-21.git8ecd47f.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-f5cdae8c6f
I'm seeing this on RHEL now (on the CDK) - boot up the CDK and run `atomic run projectatomic/mariadb-centos7-atomicapp --mode=fetch`. [root@rhel-cdk ~]# cat /etc/redhat-release Red Hat Enterprise Linux Server release 7.2 (Maipo) [root@rhel-cdk ~]# rpm -q docker atomic docker-1.9.1-25.el7.x86_64 atomic-1.9-4.gitff44c6a.el7.x86_64
And it was fixed in https://github.com/projectatomic/docker/pull/98 as indicated by Antonio.
docker-1.10.3-21.git8ecd47f.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-f5cdae8c6f
docker-1.10.3-22.git4158ccc.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-6472a8cdc7
docker-1.10.3-22.git4158ccc.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-6472a8cdc7
docker-1.10.3-23.gitf476348.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-d73f74a557
docker-1.10.3-24.gitf476348.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-6a0d540088
docker-1.10.3-24.gitf476348.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-6a0d540088
docker-1.10.3-24.gitf476348.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.