Sprakle

For about the last year, every couple months some of my docker containers would disappear from the list in the docker tab. The containers weren't just stopped, but removed from the list of containers. Thankfully no data was lost, and I could always restore them by adding a new container and selecting the template of the lost container. When restored with the template, the containers launch normally with no errors. This happens most often with HomeAssistant, but would also occur with Calibre and Radarr. Looking at the diagnostics syslog.txt, I found this would always happen after a container auto update. In syslog this would appear as "Aug 24 04:21:50 EggsBenjamin Docker Auto Update: Restarting homeassistant". After this point, the container would be removed from the list with no other error or warning I could find. From the terminal when I run "docker ps -a" the container also doesn't appear. Presumably the container is failing to start, but I don't know where to find logs showing details if the container is being removed. Any ideas? eggsbenjamin-diagnostics-20260824-0824.zip

Oh thanks for noticing that! Okay this makes sense, I'll try swapping the drive.

I've noticed recently that many of my docker containers have been stopping unexpectedly. These are common official docker containers such as NodeRed and Plex. They all stop for the same reason - docker healthcheck failure due to the error: "Output": "ttrpc: closed: unknown" I found the error with the "docker inspect" command. Interestingly, only docker containers with a healthcheck set are failing. This started happening after updating Unraid to 7.2.0 - I don't remember what version I was on before, but it was at least 6 months older. I've tried searching docker forums for similar issues, but the only relevant one I could find was fixed 5 years ago: https://github.com/containerd/containerd/issues/4483 Any ideas? UPDATE (Edit because I can't post more than once a day yet) I'm starting to see other docker containers stop for different reasons now too: docker: Error response from daemon: failed to create task for container: failed to start shim: start failed: SIGBUS: bus error Exit Code 137 It sort of sounds like an OOM error, but I'm not even close to the limits (Docker is using 3GB, I have around 10GB free). eggsbenjamin-diagnostics-20251107-1052.zip