Hide Forgot
Description of problem: Docker randomly fails to start a container with a message like this: > Cannot start container 0a9aab2b4bf2e853ba2ac6a110027c65889924b6394290418a070dc510d17a4c: [9] System error: read parent: connection reset by peer This bug is reported upstream: https://github.com/docker/docker/issues/14203 And fixed here: https://github.com/opencontainers/runc/pull/508 Another possible workaround: https://github.com/n1koo/docker/commit/8bca4f2863520f4154a15a3b3199284fe882dfda Version-Release number of selected component (if applicable): -bash-4.3# rpm -q docker docker-1.10.3-52.git8b7fa4a.fc24.x86_64 -bash-4.3# atomic host status State: idle Deployments: ● fedora-atomic:fedora-atomic/24/x86_64/docker-host Version: 24.55 (2016-10-03 16:57:50) Commit: 425570f8ef1880eabbe55154f4ddab6f99349aa5504057c8ebc588f9e769c33b OSName: fedora-atomic How reproducible: The reproducibility depends on the exact length of the JSON between runc and the container. See upstream bug.
Related log messages: Oct 19 10:10:16 localhost.localdomain.localdomain docker[1556]: time="2016-10-19T10:10:16.749595857Z" level=error msg="error locating sandbox id 4560ac0bccc6c238e88671d4351df76857c98b48f9fdeef65ff4f51a2f4c9b01: sandbox 4560ac0bccc6c238e88671d4351df76857c98b48f9fdeef65ff4f51a2f4c9b01 not found" Oct 19 10:10:16 localhost.localdomain.localdomain docker[1556]: time="2016-10-19T10:10:16.753174202Z" level=warning msg="failed to cleanup ipc mounts:\nfailed to umount /var/lib/docker/containers/0a9aab2b4bf2e853ba2ac6a110027c65889924b6394290418a070dc510d17a4c/shm: invalid argument" Oct 19 10:10:16 localhost.localdomain.localdomain docker[1556]: time="2016-10-19T10:10:16.753346217Z" level=error msg="Error unmounting container 0a9aab2b4bf2e853ba2ac6a110027c65889924b6394290418a070dc510d17a4c: not mounted" Oct 19 10:10:16 localhost.localdomain.localdomain docker[1556]: time="2016-10-19T10:10:16.753739961Z" level=error msg="Handler for POST /v1.12/containers/0a9aab2b4bf2e853ba2ac6a110027c65889924b6394290418a070dc510d17a4c/start returned error: Cannot start container 0a9aab2b4bf2e853ba2ac6a110027c65889924b6394290418a070dc510d17a4c: [9] System error: read parent: connection reset by peer"
I thought we already fixed this :/ maybe we did this just for rhel
No, we didn't fix this in rhel either..
Mrunal, do you remember anything about this?
Finally found https://bugzilla.redhat.com/show_bug.cgi?id=1339164 which is the same and claims to be fixed in docker-1.10. The original upstream commit is https://github.com/opencontainers/runc/pull/515/commits/ddcee3cc2a2ffb3ab8c630fd62689fd14ce82e07 and it's in the fedora-1.10.3 branch.
Yes, I had backported this fix to our docker branches.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.