docker exec failed！！error from pipe caused \"read parent: connection reset by peer\"问题

一、复现报错：

docker exec -it  wsqtest  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\""

二、个人问题描述：

aws社区版centos7.4装完docker，dockers pull  ${images}后，docker run ${images}，docker exec 一直进不去容器，版本如下：

 

 

三、网上类似问题：

I'm trying to execute bash in my docker container called "bind" via

docker exec -it bind bash

I'm getting the following error message:

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\""

There's nothing extraordinary in the logs. Restarting docker or the container seemed to have no effect. I also made sure that there's enough space on the hard drive. Starting any other binary in the container yields the same error.

version info:

docker --version:

Docker version 1.13.1, build 07f3374/1.13.1

OS:

cat /etc/redhat-release 

CentOS Linux release 7.6.1810 (Core) 

Any help would be appreciated.

四、解决方案：

（1）

it seems to be a bug introduced in a recent update to the docker RPM packages. A temporary workaround is to downgrade all docker packages to a previous release (75 seems to work).

yum downgrade docker-1.13.1-75.git8633870.el7_5 \
              docker-client-1.13.1-75.git8633870.el7_5 \
              docker-common-1.13.1-75.git8633870.el7_5 \
              docker-rhel-push-plugin-1.13.1-75.git8633870.el7_5

（2）

if you use

yum update

before and no idea for what the old version of docker, just run

yum downgrade docker docker-client docker-common

it work for me

share improve this answer

 

 

 

 

参考连接：

https://stackoverflow.com/questions/53605666/cannot-run-command-in-docker-container/53606269

yum downgrade docker docker-client docker-common

 

转载于:https://www.cnblogs.com/huanglinxin/p/10080622.html