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:

When container is created using podman run -ti, then podman exec seems to assume console even if the podman exec does not specify -t.

Version-Release number of selected component (if applicable):

podman-0.10.1.3-5.gitdb08685.el8+2131+7e3e9e07.x86_64

How reproducible:

Determinist.c

Steps to Reproduce:
1. In one terminal:
   podman run --name test --rm -ti registry.access.redhat.com/rhel8-beta sleep 10
2. In another terminal:
   podman exec test date < /dev/null

Actual results:

exec failed: provided file is not a console
exit status 1

Expected results:

Sat Dec  1 09:06:01 UTC 2018

Additional info:

When the container is created with podman run without -ti, podman exec then works as expected. But how podman run is started should not affect subsequence exec's.

This is fixed upstream with https://github.com/containers/libpod/commit/fd014029300328c27ddb535d4868858ec47530f8

Fixed in podman 1.0

Can reproduced with the given version in the bug. And test with podman-1.4.2-5.module+el8.1.0+4240+893c1ab8.x86_64, it works as expect. So set this to verified.
Details:
# podman run --name test --rm -ti registry.access.redhat.com/rhel8-beta sleep 10
# podman exec test date < /dev/null
Fri Sep 27 06:16:00 UTC 2019

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:3403