After 'Got a signal from the OS: "terminated"' container had to restart manually

One of my nodes stopped with error message: Got a signal from the OS: “terminated”

Restarting the Docker container helped and it is running fine.

Is there a way to make Docker automatically restart in such cases?

This message is happening when someone or something call to stop the storagenode.
Perhaps it’s watchtower or selfmade scheduled job.

It seems that this condition made entire Docker stop:

localhost dockerd[1374]: runtime: out of memory: cannot allocate 1932746752-byte block (1525383168 in use)

I have found the Docker service file in the meantime and will check the settings. It seems they need some tweaking as Docker did not start correctly after that exit.

This is a rare case, but could happen if you use a SMR disks or disk want to die.

Oh no, suicidal disks are the worst :rofl:

On a serious note, I can confirm this happened to me in the past because my SMR disk could not keep up.


It happened today again. I will try now if these settings will help:

or this:

Do you know if --memory or --memory-swap have to be at a specific position of the run command?

It should be before the image name

1 Like