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

时间: 12-06

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

ssh远程的时候出现Read from socket failed: Connection reset by peer

原因:/etc/ssh/下没有ssh*key*文件 解决: ssh-keygen -t rsa -f /etc/ssh/ssh_host_rsa_key ssh-keygen -t dsa -f /etc/ssh/ssh_host_dsa_key ssh-keygen -t ecdsa -f /etc/ssh/ssh_host_ecdsa_key 然后再尝试远程连接,显示成功 或者 直接重启服务 systemctl restart sshd

Jmeter遇到线程链接被重置(Connection reset by peer: socket write error)的解决方法

做性能测试的时候遇到一个很奇怪的问题,多线程的计划,有一个线程第一次能跑过,第二次确跑不过,单独跑这个线程跑多少次都没有问题,把思考时间改短也没有问题,唯独出现在特定的状态下,特定状态是啥,也不得而知,反正是几个设置叠加再一起碰巧出现...我就郁闷了...墙外的朋友貌似都有人遇到,墙内的没搜到,所以写了这样一篇文章简单记录一下,解决方法: 现象如图 第一次成功,第二次失败,所以错误率是50% 取样器的结果是这样的: 具体的错误信息: 看上去像是jmeter的bug,百思不得其解.google之.

解决error104 connection reset by peer;socket error问题

这个问题原因有两个: 1.因为你访问网站太多次,所以被网站管理员给禁止访问了. 解决方法: 1.延长time.sleep时间 2.设置代理 2.根本没有这个网站.(打开链接检查一下!!!)

在VMware8.0.4安装centos6.3出现蓝屏,显示“anaconda: Fatal IO error 104 (Connection reset by peer) on X server :1.0. install exited abnormally [1/1]”?

解决方案:在创建虚拟机时选择“自定义(高级)”,然后点击“下一步”,在弹出的对话框中,在硬件兼容性该项选择 Workstation6.5-7.x.如果创建虚拟机时选择“标准”,默认的硬件兼容性将是Workstation8.0,就会报错.

TNS-12547 Linux Error: 104: Connection reset by pe (转载)

TNS-12547 Linux Error: 104: Connection reset by peer 解决过程参考:http://blog.chinaunix.net/u/7121/showart_403812.html [[email protected] log]$ lsnrctl startLSNRCTL for Linux: Version 10.2.0.1.0 - Production on 23-JUN-2009 09:53:26 Copyright (c) 1991, 2005

Docker exec与Docker attach

.. 声明: 本博客欢迎转发,但请保留原作者信息! 博客地址:http://blog.csdn.net/halcyonbaby 新浪微博:@寻觅神迹 内容系本人学习.研究和总结,如有雷同,实属荣幸! ================== Docker exec与Docker attach 不论是开发者是运维人员,都经常有需要进入容器的诉求. 目前看,主要的方法不外乎以下几种: 1. 使用ssh登陆进容器 2. 使用nsenter.nsinit等第三方工具 3. 使用docker本身提供的工具 方

docker exec的具体执行流程

首先,做一个docker exec的请求: docker exec -it 5504f937f7bb sh 对应的docker -d(启动的docker daemon)的输出为: INFO[0211] POST /v1.20/containers/5504f937f7bb/exec      INFO[0211] POST /v1.20/exec/fc9c11ae6ac4827ea507e885c888bdb37c8f7b906347b9272adf8d580a6417df/start  INF

docker exec重启容器内部服务遇到的问题

起因:因为更改ldap域名,老的ldap服务器还是不断有请求发过来,经过排查发现是虚拟机的nslcd发过来的请求,但是nslcd服务配置中配置的是域名而不是ldap的ip地址,试了一下,重启服务才能去连接新的ldap服务,但是由于虚拟机众多,一个一个执行时灰常傻X的,所以打算用docker exec来循环执行,但是执行遇到了问题,如下 [[email protected] ~]# for i in tianpei.wang_172.16.162.105; do docker exec -i $i

usr/bin/mysqladmin: refresh failed; error: 'Unknown error'

debian wheezy 升级后, 因为授权错误, 导致密码给修改, 在debian的mysql safe下也无法进入. 我在/etc/mysql/my.cnf 里面已经修改了bind-address 为局域网ip 进而执行了 GRANT ALL PRIVILEGES ON *.* TO 'root'@'%' IDENTIFIED BY '123456' WITH GRANT OPTION; 然后重载授权表: FLUSH PRIVILEGES; 然后重启后, 虽然可以远程链接, 但是debia

Socket.IO failed: Error during WebSocket handshake:

在node安装了Socket.IO,做demo时报错 WebSocket connection to 'ws://localhost:8999/socket.io/?EIO=3&transport=websocket&sid=D0fxLuPwjHWgYSI7AAAB' failed: Error during WebSocket handshake: Unexpected response code: 400 WebSocket 握手时发生错误,诡异的是我前端页面没有关闭,重启服务器nod