May 31, 20197 yr After a while my unraid/dockter will stop working, and i can see in unraid my CPU is maxed out, saying 90-100% all the time. What going on, ? Can anyone help? In the logs it says time="2019-05-29T18:36:21+02:00" level=info msg=serving... address="/var/run/docker/containerd/docker-containerd-debug.sock" time="2019-05-29T18:36:21+02:00" level=info msg=serving... address="/var/run/docker/containerd/docker-containerd.sock" time="2019-05-29T18:36:21+02:00" level=info msg="containerd successfully booted in 0.116599s" time="2019-05-29T18:37:04+02:00" level=info msg="shim docker-containerd-shim started" address="/containerd-shim/moby/9d5df0e6480fa4bfdf521d74f310337a83ae4d60b2bac772ef3923b1eed3c94e/shim.sock" debug=false pid=5524 time="2019-05-29T18:37:07+02:00" level=info msg="shim docker-containerd-shim started" address="/containerd-shim/moby/2b3ba07cedcbe9b393b1c6807bde388ef7a5223a16a68659ec93ae37a7ae9358/shim.sock" debug=false pid=5761 time="2019-05-29T18:37:11+02:00" level=info msg="shim docker-containerd-shim started" address="/containerd-shim/moby/d4da9a450caeec85885461059674cd2bdf2b13d6b89e8bc5d9ac3a75fbece717/shim.sock" debug=false pid=6042 time="2019-05-29T18:37:15+02:00" level=info msg="shim docker-containerd-shim started" address="/containerd-shim/moby/507bab4b156e364b7fbc770acbdf83a846bb00286cc4b6a75fb0e828f212e0df/shim.sock" debug=false pid=6346 time="2019-05-29T18:37:20+02:00" level=info msg="shim docker-containerd-shim started" address="/containerd-shim/moby/c8dd10255cff800609fc7acb9ac857105f10940bd9957b4ad58478935d10eb25/shim.sock" debug=false pid=6724 time="2019-05-29T18:37:26+02:00" level=info msg="shim docker-containerd-shim started" address="/containerd-shim/moby/e10931b17783e2a64e6e46c975bc4eb71e142f18f9f6e82ea40735143f469b9c/shim.sock" debug=false pid=7147 time="2019-05-29T18:37:31+02:00" level=info msg="shim docker-containerd-shim started" address="/containerd-shim/moby/68df25fdd6ee4752ff7b838e37593ef722960d913f84eab5e307fbcbc024c707/shim.sock" debug=false pid=7582 time="2019-05-29T18:37:37+02:00" level=info msg="shim docker-containerd-shim started" address="/containerd-shim/moby/2f47a396ca50c4090047a6ac9ac0d78a542a8f2b6b76d4744997edfb2edae7a4/shim.sock" debug=false pid=8114 time="2019-05-29T18:37:47+02:00" level=info msg="shim docker-containerd-shim started" address="/containerd-shim/moby/4c1213043b0e386da68e1bff9bcb49dc207270139bdd8553c98e72c3613c4af6/shim.sock" debug=false pid=8816 time="2019-05-29T18:37:59+02:00" level=info msg="shim docker-containerd-shim started" address="/containerd-shim/moby/b875621ca139e71c58fe5e539e806bad1c3f8a4d7c9de58c605ce6582a0bc96c/shim.sock" debug=false pid=9820 time="2019-05-30T06:01:19+02:00" level=info msg="shim reaped" id=c8dd10255cff800609fc7acb9ac857105f10940bd9957b4ad58478935d10eb25 time="2019-05-30T06:01:51+02:00" level=info msg="shim docker-containerd-shim started" address="/containerd-shim/moby/6f51e6d38dc12daae50ce39fde5162b11abb77349ac915207ddb3bfafd96847d/shim.sock" debug=false pid=22960 time="2019-05-31T08:11:00.882927907+02:00" level=error msg="stream copy error: reading from a closed fifo" time="2019-05-31T08:11:00.882929151+02:00" level=error msg="stream copy error: reading from a closed fifo" time="2019-05-31T08:11:17.018218166+02:00" level=error msg="stream copy error: reading from a closed fifo" time="2019-05-31T08:11:17.018234872+02:00" level=error msg="stream copy error: reading from a closed fifo" time="2019-05-31T08:11:28.253736448+02:00" level=error msg="stream copy error: reading from a closed fifo" time="2019-05-31T08:11:28.253731433+02:00" level=error msg="stream copy error: reading from a closed fifo" time="2019-05-31T08:28:50.147768852+02:00" level=error msg="exit event" container=2f47a396ca50c4090047a6ac9ac0d78a542a8f2b6b76d4744997edfb2edae7a4 error="no such process" module=libcontainerd namespace=moby process=b9362351ba239fe2cf75cbc014f9218af423bf2220c3e5c2b21bc99c993dff90 time="2019-05-31T08:28:57.148213383+02:00" level=error msg="stream copy error: reading from a closed fifo" time="2019-05-31T08:28:57.148239725+02:00" level=error msg="stream copy error: reading from a closed fifo" time="2019-05-31T08:29:11.944387712+02:00" level=error msg="stream copy error: reading from a closed fifo" time="2019-05-31T08:29:11.944387481+02:00" level=error msg="stream copy error: reading from a closed fifo" time="2019-05-31T08:29:28.720220785+02:00" level=error msg="stream copy error: reading from a closed fifo" time="2019-05-31T08:29:28.720220780+02:00" level=error msg="stream copy error: reading from a closed fifo" time="2019-05-31T08:29:45.174654240+02:00" level=error msg="stream copy error: reading from a closed fifo" time="2019-05-31T08:29:45.174680627+02:00" level=error msg="stream copy error: reading from a closed fifo" time="2019-05-31T08:30:01.195072953+02:00" level=error msg="stream copy error: reading from a closed fifo" time="2019-05-31T08:30:01.195067877+02:00" level=error msg="stream copy error: reading from a closed fifo" time="2019-05-31T08:30:18.611044185+02:00" level=error msg="stream copy error: reading from a closed fifo" time="2019-05-31T08:30:18.611065335+02:00" level=error msg="stream copy error: reading from a closed fifo" time="2019-05-31T08:30:32.799522422+02:00" level=error msg="stream copy error: reading from a closed fifo" time="2019-05-31T08:30:32.799570710+02:00" level=error msg="stream copy error: reading from a closed fifo" time="2019-05-31T08:31:12.335925445+02:00" level=error msg="stream copy error: reading from a closed fifo" time="2019-05-31T08:31:12.335923627+02:00" level=error msg="stream copy error: reading from a closed fifo" time="2019-05-31T08:31:26.722289249+02:00" level=error msg="stream copy error: reading from a closed fifo"
June 4, 20197 yr Seems to be a low memory/daemon issue are you low on memory? Can you stop all but one container and see if it hangs? https://github.com/moby/moby/issues/29854 Edited June 4, 20197 yr by Fiservedpi
June 4, 20197 yr Author 3 hours ago, Fiservedpi said: Seems to be a low memory/daemon issue are you low on memory? Can you stop all but one container and see if it hangs? https://github.com/moby/moby/issues/29854 Yeah could be the problem. is there a way to limit the memory pr container or not let it crash because it wants more?
June 4, 20197 yr yes i believe you'll want to look at the adavnced tab on the docker page it shows the resources for each container on mine Plex is the biggest ram hog
June 4, 20197 yr 2 hours ago, deathleecher said: is there a way to limit the memory pr container https://forums.unraid.net/topic/57181-real-docker-faq/page/2/#comment-566087 https://forums.unraid.net/topic/57181-real-docker-faq/page/2/#comment-566088
Archived
This topic is now archived and is closed to further replies.