添加链接
link之家
链接快照平台
  • 输入网页链接,自动生成快照
  • 标签化管理网页链接
Collectives™ on Stack Overflow

Find centralized, trusted content and collaborate around the technologies you use most.

Learn more about Collectives

Teams

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

Learn more about Teams

OCI runtime create failed - copying bootstrap data to pipe caused write init-p: broken pipe

Ask Question

OCI runtime create failed: container_linux.go:348: starting container process caused "process_linux.go:297: copying bootstrap data to pipe caused \"write init-p: broken pipe\"": unknown

when I ran:

docker build \
  --build-arg bitbucket_pwd="$bitbucket_password" \
  --build-arg commit_datavana="$commit_sha" \
  --build-arg CACHE_BUST="$(date)" \
  -t "$name_tag" .

does anyone know what causes that error? Should I downgrade docker?

Downgrade your version from 18.06.3 to 18.06.1 and follow the instruction from this link.It will helpfull https://medium.com/@dirk.avery/docker-error-response-from-daemon-1d46235ff61d

this error was resolved in my ubuntu 14.04lts system

Thanks a million times for posting this, have been looking the whole day about that error message. – Gesias Jul 24, 2020 at 21:10 We're working on docker proof of concept before we move off our old machine and this was just what I needed. – Jeffrey Van Alstine Oct 30, 2020 at 20:45 Hi everyone, if you all find this answer is useful then ,kindly make it as approved answer, thanks – MathanKumar Apr 30, 2021 at 10:37

I had the same error when set very low memory limit on kubernetes 200m instead of 200Mi for pod :-)

Normal   Scheduled               <unknown>              default-scheduler                        Successfully assigned ingress-nginx/ingress-nginx-controller-b979fbd5-bkl2t to worker04.cluster
Warning  FailedCreatePodSandBox  12m (x4 over 12m)      kubelet, worker04.cluster  Failed to create pod sandbox: rpc error: code = Unknown desc = failed to start sandbox container for pod "ingress-nginx-controller-b979fbd5-bkl2t": Error response from daemon: OCI runtime create failed: container_linux.go:370: starting container process caused: process_linux.go:338: getting the final child's pid from pipe caused: read init-p: connection reset by peer: unknown
Warning  FailedCreatePodSandBox  12m (x9 over 12m)      kubelet, worker04.cluster  Failed to create pod sandbox: rpc error: code = Unknown desc = failed to start sandbox container for pod "ingress-nginx-controller-b979fbd5-bkl2t": Error response from daemon: OCI runtime create failed: container_linux.go:370: starting container process caused: process_linux.go:334: copying bootstrap data to pipe caused: write init-p: broken pipe: unknown
Normal   SandboxChanged          7m45s (x284 over 12m)  kubelet, worker04.cluster  Pod sandbox changed, it will be killed and re-created.
Warning  FailedCreatePodSandBox  2m45s (x152 over 11m)  kubelet, worker04.cluster  (combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = failed to start sandbox container for pod "ingress-nginx-controller-b979fbd5-bkl2t": Error response from daemon: OCI runtime create failed: container_linux.go:370: starting container process caused: process_linux.go:334: copying bootstrap data to pipe caused: write init-p: broken pipe: unknown

The kernel version and the docker version do not match. My original kernel version and docker are:

$ uname -a
Linux cn0314000510l 5.4.0-42-generic #46~18.04.1-Ubuntu SMP Fri Jul 10 07:21:24 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
$ sudo docker --version
Docker version 20.10.7, build 20.10.7-0ubuntu5~18.04.3

Then roll back the docker version and solve it:

$ docker --version
Docker version 18.09.9, build 039a7df9ba
        

Thanks for contributing an answer to Stack Overflow!

  • Please be sure to answer the question. Provide details and share your research!

But avoid

  • Asking for help, clarification, or responding to other answers.
  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.