Bug 1449497
| Summary: | 7.4: docker fails to start stopped container | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Jan Pazdziora (Red Hat) <jpazdziora> | |
| Component: | docker | Assignee: | Mrunal Patel <mpatel> | |
| Status: | CLOSED ERRATA | QA Contact: | atomic-bugs <atomic-bugs> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | 7.4 | CC: | amurdaca, cevich, dperpeet, jpazdziora, lsm5, lsu, mjenner, mnguyen, mpatel, qcai, santiago | |
| Target Milestone: | beta | Keywords: | Extras, Regression | |
| Target Release: | --- | |||
| Hardware: | All | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1451079 (view as bug list) | Environment: | ||
| Last Closed: | 2017-08-02 00:11:21 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1451079 | |||
|
Description
Jan Pazdziora (Red Hat)
2017-05-10 07:15:27 UTC
Some commit in docker-runc introduced this regression. Bisecting indicated this is the culprit. https://github.com/projectatomic/runc/commit/e6f0161fcd389a03f41f86746807e9a45dac050b Still present in docker-1.12.6-23.git62520c0.el7 Mrunal do you know why that commit in runc broke this? https://github.com/projectatomic/runc/commit/e6f0161fcd389a03f41f86746807e9a45dac050b I am seeing something that might be related to this BZ when running a private registry container with --restart=always. # docker run -d -p 5000:5000 --restart=always --name registry registry:2 Unable to find image 'registry:2' locally Trying to pull repository registry.access.redhat.com/registry ... Trying to pull repository docker.io/library/registry ... 2: Pulling from docker.io/library/registry 79650cf9cc01: Pull complete 70ce42745103: Pull complete 77edd1a7fa4d: Pull complete 432773976ace: Pull complete 3234a47fe5a9: Pull complete Digest: sha256:a3551c422521617e86927c3ff57e05edf086f1648f4d8524633216ca363d06c2 6b51a64cecb9b7757d3474e34c248478470b3325cc21e91df6143d6383b1db72 # docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 6b51a64cecb9 registry:2 "/entrypoint.sh /etc/" 5 seconds ago Up 4 seconds 0.0.0.0:5000->5000/tcp registry # systemctl restart docker # docker images REPOSITORY TAG IMAGE ID CREATED SIZE docker.io/registry 2 9d0c4eabab4d 4 days ago 33.17 MB [root@rhelah ~]# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES [root@rhelah ~]# docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 6b51a64cecb9 registry:2 "/entrypoint.sh /etc/" 32 seconds ago Exited (2) 21 seconds ago registry [root@rhelah ~]# docker start registry Error response from daemon: invalid header field value "oci runtime error: container with id exists: 6b51a64cecb9b7757d3474e34c248478470b3325cc21e91df6143d6383b1db72\n" Error: failed to start containers: registry # rpm -qa docker docker-1.12.6-26.git62520c0.el7.x86_64 Found the root cause. I am working on a fix for this. Here is the PR for the fix: https://github.com/projectatomic/runc/pull/7 *** Bug 1451923 has been marked as a duplicate of this bug. *** Looks fine in docker-1.12.6-41.1.gitf55a118.el7.x86_64 # docker start -a date Sat Jul 8 07:29:42 UTC 2017 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:2344 |