Originally published on my blog — read it there with the full context, code and updates .

The notification I expected to be a config mistake

My NAS sent the notification every Docker user learns to skim: container

stopped unexpectedly . This one is the edge proxy in front of my

self-hosted wiki, and it had been up for two weeks. Nobody had deployed

anything that morning and nothing in the compose file had been touched, so

the two available stories were "it crashed" and "something restarted it".

Both were wrong, and the fact that I could not tell from Docker's own report

is the part worth writing down.

Docker's report says nothing happened

State: Status: running Running: true ExitCode: 0 <- a clean exit OOMKilled: false <- not killed by the kernel FinishedAt: 2026-10-15T19:39:33.63057879Z StartedAt: 2026-10-15T19:39:38.769326672Z <- restarted 5 s later RestartCount: 6 RestartPolicy: always

Enter fullscreen mode

Exit fullscreen mode

Read that as written and the conclusion is: the process exited…