Logread spammed by dockerd/containerd

Installing and Using OpenWrt
1

My logs are being filled up with containerd messages.

# logread | grep containerd | wc -l
326

Sun Feb 16 08:05:48 2025 daemon.err dockerd[9333]: time="2025-02-16T08:05:48.794027723Z" level=info msg="loading plugin \"io.containerd.event.v1.publisher\"..." runtime=io.containerd.runc.v2 type=io.containerd.event.v1
Sun Feb 16 08:05:48 2025 daemon.err dockerd[9333]: time="2025-02-16T08:05:48.794161175Z" level=info msg="loading plugin \"io.containerd.internal.v1.shutdown\"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1
Sun Feb 16 08:05:48 2025 daemon.err dockerd[9333]: time="2025-02-16T08:05:48.794194742Z" level=info msg="loading plugin \"io.containerd.ttrpc.v1.task\"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1
Sun Feb 16 08:05:48 2025 daemon.err dockerd[9333]: time="2025-02-16T08:05:48.794400340Z" level=info msg="loading plugin \"io.containerd.ttrpc.v1.pause\"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1
Sun Feb 16 08:05:48 2025 daemon.err dockerd[9333]: time="2025-02-16T08:05:48.946734225Z" level=warning msg="cleaning up after shim disconnected" id=45656bd157d8633c2209cf1858253d53e3d83e0c2f2d19fae71d939c2ec84445 namespace=moby

I tracked this down to a container restarting rapidly on my system.

I notice that this has been changed from info to debug upstream: https://github.com/containerd/containerd/pull/9646

2

hi,

and what is the problem? dockerd reports information as should i see no problem here. could you please elaborate?

1 Like
3

Firstly, containerd should be updated from upstream so it's logging at the right level, and secondly I would prefer that my logs are as quiet as possible.

4

rapidly restarting container is a problem, you are notified that's totally normal and expected. the other way around would be weird. but you can use other syslog manager than default logd and hide these information if you wish.

1 Like