Bug 1655211

Summary: podman exec seems to assume console even if -ti is not used
Product: Red Hat Enterprise Linux 8 Reporter: Jan Pazdziora (Red Hat) <jpazdziora>
Component: podmanAssignee: Brent Baude <bbaude>
Status: CLOSED ERRATA QA Contact: atomic-bugs <atomic-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.0CC: ddarrah, dornelas, dwalsh, jligon, lsm5, mheon, ypu
Target Milestone: rc   
Target Release: 8.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: podman-1.4.2 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-05 21:00:57 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:
Bug Depends On:    
Bug Blocks: 1186913, 1734574    

Description Jan Pazdziora (Red Hat) 2018-12-01 09:08:04 UTC 
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.
Comment 1 Matthew Heon 2018-12-06 18:25:10 UTC 
This is fixed upstream with https://github.com/containers/libpod/commit/fd014029300328c27ddb535d4868858ec47530f8
Comment 2 Daniel Walsh 2019-01-10 21:05:33 UTC 
Fixed in podman 1.0
Comment 5 Joy Pu 2019-09-27 06:29:13 UTC 
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
Comment 7 errata-xmlrpc 2019-11-05 21:00:57 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-2019:3403