Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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'.
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.
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.
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'.