Bug 1655975

Summary: docker exec command is failing for Ubuntu , busybox containers
Product: Red Hat Enterprise Linux 7 Reporter: Lalatendu Mohanty <lmohanty>
Component: dockerAssignee: Daniel Walsh <dwalsh>
Status: CLOSED DUPLICATE QA Contact: atomic-bugs <atomic-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 7.6CC: amurdaca, arghosh, dornelas, fshaikh, jpazdziora, lsm5, maschmid, philipp.dallig, rhbz, ruben, travi
Target Milestone: rcKeywords: Extras
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-12-04 21:12:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Lalatendu Mohanty 2018-12-04 10:54:56 UTC
Description of problem:

docker exec command on Ubuntu container is failing.

However, it works fine on CentOS container inages

Version-Release number of selected component (if applicable):
docker 1.13.1-84.git07f3374 (RPM version i.e. rpm -qa | grep docker)

How reproducible:

Always

Steps to Reproduce:
On RHEL 7.6 run following commands

1. docker run -ti --rm ubuntu bash
2. Open a new tab 
3. run the "docker ps" command and note the container ID for the Ubuntu container
4. Run "docker exec -ti <Container ID> bash"

Actual results:

$ docker exec -ti 015c6ad3c816 bash

rpc error: code = 2 desc = oci runtime error: exec failed: container_linux.go:247: starting container process caused "process_linux.go:110: decoding init error from pipe caused \"read parent: connection reset by peer\""




Expected results:

docker exec command should run without any issue

Additional info:

The issue is coming with docker 1.13.1-84.git07f3374 (RPM version), but we cannot reproduce the same issue with docker 1.13.1-75.git8633870. 

We got this while testing latest CDK build based on latest RHEL 7 : https://issues.jboss.org/browse/CDK-380

There is an existing Origin issue on this https://github.com/openshift/origin/issues/21590

Comment 2 Lalatendu Mohanty 2018-12-04 11:06:27 UTC
It is also failing for busybox

$ docker run -ti --rm busybox sh 

In a new shell 
$ docker exec -ti 55d7f58509b6 sh  
rpc error: code = 2 desc = oci runtime error: exec failed: container_linux.go:247: starting container process caused "process_linux.go:110: decoding init error from pipe caused \"read parent: connection reset by peer\""

Comment 3 Ruben Vermeersch 2018-12-04 12:08:24 UTC
This breaks all Kubernetes clusters as well, so pretty critical!

Comment 4 Jan Pazdziora 2018-12-04 15:41:05 UTC
This looks like duplicate of bug 1655214.

Comment 5 Derrick Ornelas 2018-12-04 21:12:23 UTC

*** This bug has been marked as a duplicate of bug 1655214 ***