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

shareimprove 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

时间: 2024-11-08 09:51:36

docker exec failed!!error from pipe caused \"read parent: connection reset by peer\"问题的相关文章

java.net.SocketException: recvfrom failed: ECONNRESET (Connection reset by peer)

java.net.SocketException: recvfrom failed: ECONNRESET (Connection reset by peer)11-22 14:49:16.870: WARN/System.err(3581):     at libcore.io.IoBridge.maybeThrowAfterRecvfrom(IoBridge.java:542)11-22 14:49:16.870: WARN/System.err(3581):     at libcore.

CentOS7使用ssh不能登录,报错:Read from socket failed: Connection reset by peer

使用xshell登录CentOS7,不能登录,使用另外一台Linux主机,telent 22端口是同的,ssh连接报以下错误: Read from socket failed: Connection reset by peer 查看不能登录主机的日志 # cat /var/log/messages Dec 15 19:38:27 localhost dbus-daemon: dbus[874]: [system] Successfully activated service 'org.freed

recv() failed (104: Connection reset by peer) while reading response header from upstream

场景: 为了得到用户在线等信息,在客户端做了个ajax轮训: 于是问题就来了, 日志文件 [[email protected] web]# tail -f /data/log/nginx_error.log 2017/06/16 19:20:28 [error] 230555#0: *10228041 recv() failed (104: Connection reset by peer) while reading response header from upstream,client:

OGG-01232 Receive TCP params error: TCP/IP error 104 (Connection reset by peer), endpoint:

源端: 2015-02-05 17:45:49 INFO OGG-01815 Virtual Memory Facilities for: COM anon alloc: mmap(MAP_ANON) anon free: munmap file alloc: mmap(MAP_SHARED) file free: munmap target directories: /home/ggt/goldengate/dirtmp. CACHEMGR virtual memory values (may

SSH 错误解决案例1:Read from socket failed: Connection reset by peer

今天早上天天连接的开发机突然报出连接错误. 这个错误是SSH最常见错误,造成的原因也是千奇百怪(具体可goole),下面描述我的server的问题: 客户端报错 [[email protected]]# ssh 192.168.1.22 Read from socket failed: Connection reset by peer 换个机器连接也不行,尝试重启server端的sshd,thanks god, 报错了 [[email protected] ssh]# service sshd

老项目采用tomcat出现异常:Connection reset by peer: socket write error 异常解决方法

项目一段时间就出现异常,导致无法登陆系统,数据库无法连接上 异常信息如下: java.sql.SQLException: Io 异常: Connection reset by peer: socket write error at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134) at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179) a

OGG-01232 Receive TCP Params Error: TCP/IP Error 104 (Connection Reset By Peer).

经常在OGG日志文件中看到如下错误: 查了metalink,大概说的是extract 和collector 交互的关系,分为STREAMING 和NOSTREAMING 模式,各有各的优势.总的建议如果该错误不是很频繁,建议使用STREAMING模式.下面贴出原文: OGG-01232 Receive TCP Params Error: TCP/IP Error 104 (Connection Reset By Peer). (文档 ID 1684527.1) 转到底部 In this Docu

LR回放https协议脚本失败:[GENERAL_MSG_CAT_SSL_ERROR]connect to host "XXX" failed:[10054] Connection reset by peer [MsgId:MERR-27780]

最近做一个负载均衡项目的性能测试,使用LR录制脚本协议为https协议,回放脚本时出现报错: [GENERAL_MSG_CAT_SSL_ERROR]connect to host "XXX" failed:[10054] Connection reset by peer  [MsgId:MERR-27780] 如图: Loadrunner默认发送是通过sockets(将http转换为sockets)发送的,而sockets默认SSL的版本为SSL2和SSL3.HTTPS协议录制的脚本以

connection reset by peer, socket write error问题分析

上次写<connection reset by peer, socket write error问题排查>已经过去大半年,当时把问题"敷衍"过去了. 但是此后每隔一段时间就会又想起来,baidu.google一番,可能也会再拉周围的人小讨论一下,然后无果而终.淡忘,想起,淡忘,又想起,挥之不去. 这个周末它又在脑海中浮现,这次总算理解了这个问题,答案就在一本买了很久的新书<HTTP权威指南>中.如果懒得看下面的啰嗦,可以去直接看书中的<4.7.4 正常关闭