I have an issue where /run keeps filling up and therefore my docker containers will turn unhealthy. After some digging i have found that this is the offending file: /run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/1669b11159d872bda4662dd88a0848ea89c988cc3dd4589b0365f623c8cdfedf/log.json

 

Looking in the config.json and options.json in the same directory I worked out that this is my Plex container. 

 

Sample of logs below, this keeps on going until the drive is full:

 

{"level":"info","msg":"Using low-level runtime /usr/bin/runc","time":"2022-10-04T09:59:15+01:00"}
{"level":"info","msg":"Using low-level runtime /usr/bin/runc","time":"2022-10-04T09:59:20+01:00"}
{"level":"info","msg":"Using low-level runtime /usr/bin/runc","time":"2022-10-04T09:59:25+01:00"}
{"level":"info","msg":"Using low-level runtime /usr/bin/runc","time":"2022-10-04T09:59:31+01:00"}
{"level":"info","msg":"Using low-level runtime /usr/bin/runc","time":"2022-10-04T09:59:36+01:00"}
{"level":"info","msg":"Using low-level runtime /usr/bin/runc","time":"2022-10-04T09:59:41+01:00"}
{"level":"info","msg":"Using low-level runtime /usr/bin/runc","time":"2022-10-04T09:59:46+01:00"}
{"level":"info","msg":"Using low-level runtime /usr/bin/runc","time":"2022-10-04T09:59:51+01:00"}
{"level":"info","msg":"Using low-level runtime /usr/bin/runc","time":"2022-10-04T09:59:57+01:00"}
{"level":"info","msg":"Using low-level runtime /usr/bin/runc","time":"2022-10-04T10:00:02+01:00"}
{"level":"info","msg":"Using low-level runtime /usr/bin/runc","time":"2022-10-04T10:00:07+01:00"}
{"level":"info","msg":"Using low-level runtime /usr/bin/runc","time":"2022-10-04T10:00:12+01:00"}
{"level":"info","msg":"Using low-level runtime /usr/bin/runc","time":"2022-10-04T10:00:17+01:00"}
{"level":"info","msg":"Using low-level runtime /usr/bin/runc","time":"2022-10-04T10:00:22+01:00"}

 

I have checked plex is running fine and docker is reporting the container as healthy 

1669b11159d8   plexinc/pms-docker:plexpass             "/init"                  3 weeks ago    Up 2 weeks (healthy)
 

Anyone know why this message might be constantly repeating? 

 

Diag Attached

unraid01-diagnostics-20221004-1004.zip

Ever find a solution to this problem? I'm experiencing the same thing.

I was able to identify the cause of the repeated log entries in the debug.log file for me were related to Plex's healthcheck. The --no-healthcheck option can be used to disable the healthcheck mechanism in Docker. By default, Docker performs a healthcheck on each container to ensure that the container's main process is running and healthy. If the healthcheck fails, Docker can take appropriate action, such as restarting the container.

 

In my case, it seems that the healthcheck mechanism is causing repeated log entries in the debug.log file. Disabling the healthcheck seems to be a workaround for this issue, but it's more of a band-aid than a solution. If the main process of the container crashes or becomes unresponsive, Docker may not be able to detect the issue and take appropriate action.

 

To implement the work-around, edit your Plex container, toggle the 'advanced' setting using the switch in the top right of the page, and add --no-healthcheck to the 'Extra Parameters'.

 

I hope this helps others, but if somebody knows more about how to troubleshoot the actual problem where healthcheck causes excessive logging, I'd greatly appreciate it.

 

Thanks @Indmenity83! I had this issue where the Plex container was logging to log.json and filling up /run which caused problems with all containers not starting (found that from here) 

 

I was deleting the log.json file manually but bow this --no-healthcheck option prevents it from happening.

 

Would love to know if this is happening because of something else being wrong or if it's a bug that should be fixed.