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.

Description of problem:
As described in https://github.com/kubernetes/kubernetes/issues/61557, it is possible for docker/moby to hang when hijacking a connection with input as it never properly closes the connection at the end of the stream.

This is resolved in upstream moby here:

https://github.com/moby/moby/pull/36517/commits/37983921c90b468cafd3ba2ca2574fb81cafe5a7#diff-59ab7cc5bb1a636a4bc611d138984608R193

Version-Release number of selected component (if applicable):
It does not appear to be in the source of the latest release available [docker-1.13.1-88.git07f3374.el7]

How reproducible:
Every time


Steps to Reproduce:
1. Run a kubectl command that will utilize docker hijacking:

  # echo -n a | kubectl exec -i mypod cat

2. Observe hang

Actual results:
Command hangs instead of closing the stream

Expected results:
Docker should close hijacked streams with proper CloseWrite() calls

Additional info:
I have not been able to test this myself yet; I only observe that we don't appear to close the stream as the commit does in postHijacked().

Backported here https://github.com/projectatomic/docker/commit/b2f74b220126bddbae585cfe2406498ced3ae065

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/RHSA-2019:0487