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.
Bug 1807379 - podman exec does not reads from stdin
Summary: podman exec does not reads from stdin
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: podman
Version: 8.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.2
Assignee: Jindrich Novy
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
: 1807589 1807590 1807591 1827324 (view as bug list)
Depends On: 1807586 1807587 1807588 1807589 1807590 1807591
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-26 09:04 UTC by Attila Fazekas
Modified: 2020-07-21 15:32 UTC (History)
12 users (show)

Fixed In Version: podman-1.9.0-1.module+el8.2.1+6336+d8c27409
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-21 15:31:54 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github containers libpod issues 4326 0 None closed podman exec stdin regression 2021-02-11 10:04:40 UTC
Red Hat Product Errata RHSA-2020:3053 0 None None None 2020-07-21 15:32:28 UTC

Description Attila Fazekas 2020-02-26 09:04:48 UTC
Description of problem:
echo foo | podman exec 2607c48ac86d cat
echo foo | podman exec -i 2607c48ac86d cat
Error: read unixpacket @->/var/run/libpod/socket/061191f3aa1a2f0c7952f8fc6201c86c30f1391e041f55ef8f17ff620ebbbd4d/attach: read: connection reset by peer


Version-Release number of selected component (if applicable):
podman-1.6.4-2.module+el8.1.1+5363+bf8ff1af.x86_64

How reproducible:
always

Upstream bug:
https://github.com/containers/libpod/issues/4326

Comment 1 Tom Sweeney 2020-02-26 16:29:08 UTC
The fix for this upstream is https://github.com/containers/libpod/pull/4818.  Jindrich I'm assigning to you for packaging, if that's too soon please let me know.

Comment 3 Derrick Ornelas 2020-03-02 18:04:38 UTC
*** Bug 1807590 has been marked as a duplicate of this bug. ***

Comment 5 Jindrich Novy 2020-04-22 07:40:23 UTC
*** Bug 1807591 has been marked as a duplicate of this bug. ***

Comment 6 Jindrich Novy 2020-04-22 07:41:23 UTC
*** Bug 1807589 has been marked as a duplicate of this bug. ***

Comment 11 Jindrich Novy 2020-04-23 16:35:32 UTC
*** Bug 1827324 has been marked as a duplicate of this bug. ***

Comment 12 Joy Pu 2020-06-02 11:13:28 UTC
Test with podman-1.9.3-1.module+el8.2.1+6750+e53a300c.x86_64. And this is working as expected. So set this to verified.
Details:
$ podman run -d busybox top
Trying to pull registry.access.redhat.com/busybox...
  name unknown: Repo not found
Trying to pull registry.redhat.io/busybox...
  unable to retrieve auth token: invalid username/password: unauthorized: Please login to the Red Hat Registry using your Customer Portal credentials. Further instructions can be found here: https://access.redhat.com/RegistryAuthentication
Trying to pull docker.io/library/busybox...
Getting image source signatures
Copying blob d9cbbca60e5f done  
Copying config 78096d0a54 done  
Writing manifest to image destination
Storing signatures
fd75b01d86f99baa113f5f8c2df473dcdd3600c894173d80b915daa3dcf3b60b
$ echo foo | podman exec -i fd75b01d86 cat
foo

Comment 14 errata-xmlrpc 2020-07-21 15:31:54 UTC
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-2020:3053


Note You need to log in before you can comment on or make changes to this bug.