Bug 1420147
| Summary: | read unix @->/var/run/docker.sock: read: connection reset by peer | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Ed Santiago <santiago> |
| Component: | docker | Assignee: | Antonio Murdaca <amurdaca> |
| Status: | CLOSED ERRATA | QA Contact: | atomic-bugs <atomic-bugs> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.3 | CC: | agoldste, amurdaca, bparees, cevich, jminter, lsm5 |
| Target Milestone: | rc | Keywords: | Extras |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | docker-1.12.6-9.el7_3 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-03-02 19:08:46 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: | |||
This backport https://github.com/projectatomic/docker/commit/e1d02aa55efa49c9d888b79f7c3ac44b5a24f72c from upstream https://github.com/docker/docker/pull/30446 caused this issue. I'm investigating a fix with upstream (since the backport is needed by openshift). Bug still present in yesterday's docker-1.12.6-3.el7 build This is still not fixed as per https://github.com/docker/docker/issues/30816 I don't have any use case in mind for such a test though and we're discussing whether to get rid of this behavior or not https://github.com/docker/docker/issues/30816#issuecomment-278311204 Fixed in docker-1.12.6 - since this is for a patch release, I don't think getting rid of this functionality is nice. Upstream still has to decide and right now, the only sane thing we can do is to return at the old behavior (with https://github.com/jim-minter/docker/commit/1aa000451ced8c0c4034e667a33efb1cc9833fc9). This is _not_ fixed in our builds of 1.12.6. CI tests still failing as of docker/docker-latest-1.12.6-8.el7.x86_64. Marking this as High and assuming higher-layers care about attaching to containers stdin/out/err not causing non-zero exits (and error messages) from the client. Blocker? I could certainly understand if it is, but that's not our call. Lokesh, could you rebuild from docker-1.12.6 branch? I don't *think* this will cause a problem for Kube/OpenShift. When Kube creates a container, it always sets OpenStdin to true if the user requests stdin. You could opt to do -i (open stdin) and --attach=false, but that would still result in OpenStdin being set to true. If we have run the OpenShift end to end tests using a version of docker that has this issue, OpenShift is probably ok. There's still a chance we're not, but I am having trouble reasoning through what scenario would cause a problem. Fix confirmed in docker-1.12.6-10.el7 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://rhn.redhat.com/errata/RHBA-2017-0406.html |
Today's docker build introduces a regression with -a (--attach) option: # echo true | docker run -a stdin -a stderr --tty=false centos read unix @->/var/run/docker.sock: read: connection reset by peer # echo $? 1 This is a regression. Expected: no output, exit status 0. Same error if we s/stderr/stdout/ but not if it's just -a stdin or just -a stdout. There may be other permutations I haven't tested. # rpm -qa|egrep 'docker|container-selinux'|sort container-selinux-2.7-1.el7.noarch docker-1.12.6-2.el7.x86_64 docker-client-1.12.6-2.el7.x86_64 ... Not SELinux-related: problem persists with 'setenforce 0'.