Synology reports unexpected behaviour

[JasonEMartin]

Hi all, I'm guessing this is more of a Synology issue than this script but will raise it for discussion.
I have a SynologyNAS running Docker. When starting the docker container, the script does as it should, updates Trakt then closes. The final line in the log 'INFO - Completed full sync in 59.0 seconds'. But after each and every run, Synology alerts with 'Error - Docker container plextraktsync stopped unexpectedly.' As I have this running every four hours, I have multiple warnings throughout the day.
Any ideas on what can be done?
Appreciate any comments, Jason

[JasonEMartin]

A little further research and I have the answer. Posting here if it helps anyone else.

The Synology Docker package will generate the notification Docker container xxxx stopped unexpectedly, if the container is considered "enabled" by the Synology Docker GUI. This information is stored in /var/packages/Docker/etc/container_name.config: as first line below

"enabled" : true,
"entrypoint_default" : "python -m plextraktsync",
"exporting" : false,
"id" : "dbee87466fb70ea26cd9845fd79af16d793dc64d9453e4eba43430594ab4fa9b",
"image" : "ghcr.io/taxel/plextraktsync:latest",
"is_ddsm" : false,
"is_package" : false,
"name" : "plextraktsync",
"shortcut" : {
"enable_shortcut" : false,
"enable_status_page" : false,
"enable_web_page" : false,
"web_page_url" : ""

Containers are automatically enabled if you start them from the GUI. All of these things will cause the container to become "enabled" and start notifying on exit:

• Sliding the "toggle switch" in the container view to "on"
• Using Action start on the container.
• Opening the container detail panel and clicking "start"

Solution
Containers can be disabled if you stop them while they are running. Therefore start it and then stop it before it exits on its own.
You can check the effect looking at the first line once again from the above container_name.config. It will have changed to "enabled": false.
And I can confirm that now, after running per schedule there are no notifications that it has stopped unexpectedly.