Docker 20.10.5 - constant error: level=error msg="copy shim log" error="read /proc/self/fd/10: file already closed"

Hey,
i lately upgraded from docker 20.10.2 to 20.10.5.
i’m running a keepalive task for my consul cluster that uses consul container:
“sudo docker run --net host --rm consul members”

all works as expected, but i get this error log every time:
Apr 04 07:50:03 ip-172-31-43-24 containerd[920]: time=“2021-04-04T07:50:03.397017672Z” level=info msg=“starting signal loop” namespace=moby path=/run/containerd/io.containerd.runtime
Apr 04 07:50:03 ip-172-31-43-24 dockerd[3775]: time=“2021-04-04T07:50:03.662612427Z” level=info msg=“ignoring event” container=fb2890d9b6eb9fcaa578786d3b1dc98a8faa6dea4e6259f0ec446d1
Apr 04 07:50:03 ip-172-31-43-24 containerd[920]: time=“2021-04-04T07:50:03.663902692Z” level=info msg=“shim disconnected” id=fb2890d9b6eb9fcaa578786d3b1dc98a8faa6dea4e6259f0ec446d1a9
Apr 04 07:50:03 ip-172-31-43-24 containerd[920]: time=“2021-04-04T07:50:03.665598022Z” level=error msg=“copy shim log” error="read /proc/self/fd/10: file already closed"

can someone help please?

thanks!

Same issue,
apline 3.13 with arai2c running in it only. Gets killed of by docker, no OOM error. But I do see the error as listed above.

Note, this only happens on hardware (Dell r710) running ubuntu 20.04 latest updates… Native and docker direct from their repo, same issue.
HOWEVER. exactly the same setup by a Dell r720, vmware 6.7, VM-running 20.04 on top, and the problem goes away.

What to do??? Would really like some help here as no idea why being docker on natice hardware and docker on VM would make any difference.

Facing the exact same issue, also on a R710.
I’m running Gentoo though, with kernel 5.10.11-gentoo

Downgrading to app-emulation/docker-20.10.3::gentoo solved my issue temporarily, but I’m concerned about future updates.

After updating the docker version (20.10.7, build f0df350), still I am getting the issue.

We’re seeing these same kinds of errors logged in our Kubernetes cluster.

I ran daemon docker (dockerd) as root instead of sudo dockerd and solved this problem temporarily.