Question Portainer on Docker... stopping container error.

Currently reading
Question Portainer on Docker... stopping container error.

1,072
356
NAS
DS418play, DS213j, DS3621+, DSM 7.0.4-11091
I wanted to stop qbittorrent and sonarr dockers and lazily chose to do that via the Prtainer docker. But Synology didn't like that... I got this notification.

Docker container qbittorrentvpn stopped unexpectedly.

I will note that these containers are linked. In Portainer, I first shutdown the linked qbittorrent/sonarr container, followed by the still running qbittorrent container. Portainer seemed content with that.

Have I done something wrong here?
 

Shadow

Subscriber
467
161
NAS
DS216+II, DS118, DS718+
Router
  1. RT2600ac
  2. MR2200ac
Operating system
  1. Windows
Mobile operating system
  1. Android
Iam getting the same. Not always, but sometimes.

I also get this error message in the syno UI if I run command 'docker container stop'.
 
"stopped unexpectedly" from the perspective of the Syno Docker UI... I always felt this is a false negative.

Would the Docker UI register a watch on the Docker event stream, it would actualy receive the termination information... Well, at least this is what their implementation should have used.

An example for good use of watches on the event stream is Traefik.. Whenever a conatiner commes up, it checks its labels and applies those instantly to its reverse proxy rules set. When a labeled container dies, it instantly removes the reverse proxy rules for this container... There is a way... Synology just needs to leverage it...
 

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Welcome to SynoForum.com!

SynoForum.com is an unofficial Synology forum for NAS owners and enthusiasts.

Registration is free, easy and fast!

Similar threads

Similar threads

Trending threads

Top