Description of problem: When container is started from image registry.access.redhat.com/rhel7:7.3, docker exec then always fails. Version-Release number of selected component (if applicable): docker-1.13.1-84.git07f3374.el7.x86_64 How reproducible: Deterministic. Steps to Reproduce: 1. docker run --name test -d --rm registry.access.redhat.com/rhel7:7.3 sleep 10 2. docker exec test date Actual results: 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: Sat Dec 1 09:42:33 UTC 2018 Additional info: This is regression against RHEL 7.5 and its docker-1.13.1-75.git8633870.el7_5.x86_64. This affects rhel7/ipa-server container upgrade testing from version rhel7/ipa-server:4.4.0. Things work with registry.access.redhat.com/rhel7:7.4 and newer.
I can reproduce. Some images are working, and some other don't: Working images: - registry.access.redhat.com/rhel7:7.4 - registry.access.redhat.com/rhel7:7.5 - registry.access.redhat.com/rhel7:7.6 - centos:7 Not working images: - registry.access.redhat.com/rhel7:7.3 - debian:9 - ubuntu:18.04 It used to work on RHEL 7.5
The problem is also present with images - registry.fedoraproject.org/fedora:rawhide - registry.fedoraproject.org/fedora:29 - registry.fedoraproject.org/fedora:28 So it looks like anything that is not recent registry.access.redhat.com/rhel7 or centos image is not usable by latest docker. Let me increate the severity and priority of this bug.
Lokesh, is this a duplicate of Bug 1650512 - podman exec faile with "panic: boringcrypto: not in FIPS mode" ?
Sorry, I meant is this related? The runc BZ is already closed with errata.
*** Bug 1655975 has been marked as a duplicate of this bug. ***
*** Bug 1655971 has been marked as a duplicate of this bug. ***
More images could be affected - for example I can reproduce this bug with image https://hub.docker.com/r/andyshinn/dnsmasq/. This issue is also mentioned on SO: https://stackoverflow.com/questions/53605666/cant-execute-bash-in-docker-container
*** Bug 1656119 has been marked as a duplicate of this bug. ***
We see this issue with centos 6.x based containers as well. Downgrade workaround works. Also upgrading to docker-1.13.1-87.git07f3374.el7.x86_64.rpm worked as well. We picked the rpms from https://cbs.centos.org/koji/buildinfo?buildID=24652
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/RHBA-2018:3796
PID=docker inspect --format {{.State.Pid}} <name of container> nsenter --target $PID --mount --uts --ipc --net --pid /bin/sh Is a possible temporary workaround to this issue