stop one docker image sending out unexpectedly shut down notifications

[darrenoakey]

so I _love_ synology's docker - and run heaps of containers. However - there is one container - a google photos sync which is scheduled to run ever hour - it syncs, _then exits_. That all works perfectly and was setup from inside the synology ui using standard functionality.

And every time it finishes - I get an error, and an email, saying that the docker image was shut down unexpectedly!?

Is there any way I can suppress that for this container? For every other container - I still very much want this alert, because it would be a surprise - but the entire point of this container is to startup and then shutdown. Any ideas how I can fix this?

Thanks!

 

[Shadow]

I also have these annoying messages since DSM7... I turned them off as I use Zabbix to monitor my environment...

 

[jeyare]

Image can’t be shutdown. It’s a container or even entire docker daemon. Follow your description it is about single container only.
You don’t have exactly described the container image source.

To find a reason of the event, check this:

Docker daemon eating up disk I/O

I'm asking this question on behalf of someone from another (Dutch) forum. Anyone seen this before and have any idea what is causing this? User is only running this container, and this disk activity only seems to hapen when this container is started: GitHub - qdm12/gluetun: VPN client in a...

www.synoforum.com

 

[darrenoakey]

I know exactly the reason the container shuts down. It's supposed to. it does its job, and finishes, until it is run again.

what I want to do is suppress the alert telling me of something behaving exactly how it is designed to behave.

 

[jeyare]

And every time it finishes - I get an error, and an email, saying that the docker image was shut down unexpectedly!?

You didn't get an error. You received just an event notification, based on your default DSM Notification setup (which is defined as Error by Synology).

There must be a reason why DSM has information from docker daemon about an "unexpected stop'.
One of them is, how you handle this container
When it's a kind of ephemeral container, then it is better to run the container by docker run --rm -i image_name, than standard docker start <containername>
...reason why was asked the container details.

Also check:

docker inspect <containername>

you need find
"ExitCode":
paste here

then you need to check docker events (as was proposed in my previous post) and find within the container events - 'die'.