Is the docker container supposed to stop running on its own?

[imsorrywhat]

Started up container in Portainer Stack using the docker-compose example. Only change was to add a container name and additional volumes that it should have access to. No errors during initial creation.

After a few days, it will show State as "exited - code 0". The logs for the container:

[xvnc        ] Thu Aug  1 14:38:19 2024
[xvnc        ]  Connections: accepted: /tmp/vnc.sock
[xvnc        ]  SConnection: Client needs protocol version 3.8
[xvnc        ]  SConnection: Client requests security type None(1)
[xvnc        ]  VNCSConnST:  Server default pixel format depth 24 (32bpp) little-endian rgb888
[xvnc        ]  VNCSConnST:  Client pixel format depth 24 (32bpp) little-endian bgr888
[xvnc        ]  VNCSConnST:  closing /tmp/vnc.sock: Clean disconnection
[xvnc        ]  EncodeManager: Framebuffer updates: 14
[xvnc        ]  EncodeManager:   Tight:
[xvnc        ]  EncodeManager:     Solid: 37 rects, 1.55501 Mpixels
[xvnc        ]  EncodeManager:            592 B (1:10507.5 ratio)
[xvnc        ]  EncodeManager:     Bitmap RLE: 22 rects, 19.732 kpixels
[xvnc        ]  EncodeManager:                 754 B (1:105.029 ratio)
[xvnc        ]  EncodeManager:     Indexed RLE: 14 rects, 47.394 kpixels
[xvnc        ]  EncodeManager:                  1.71777 KiB (1:107.87 ratio)
[xvnc        ]  EncodeManager:   Tight (JPEG):
[xvnc        ]  EncodeManager:     Full Colour: 31 rects, 411.703 kpixels
[xvnc        ]  EncodeManager:                  224.81 KiB (1:7.15529 ratio)
[xvnc        ]  EncodeManager:   Total: 104 rects, 2.03383 Mpixels
[xvnc        ]  EncodeManager:          227.842 KiB (1:34.8746 ratio)
[xvnc        ]  Connections: closed: /tmp/vnc.sock
[xvnc        ]  ComparingUpdateTracker: 0 pixels in / 0 pixels out
[xvnc        ]  ComparingUpdateTracker: (1:-nan ratio)
[supervisor  ] SIGTERM received, shutting down...
[supervisor  ] stopping service 'app'...
[supervisor  ] service 'app' exited (with status 3).
[supervisor  ] stopping service 'xcompmgr'...
[supervisor  ] service 'xcompmgr' exited (got signal SIGTERM).
[supervisor  ] stopping service 'openbox'...
[supervisor  ] stopping service 'nginx'...
[supervisor  ] service 'openbox' exited (with status 0).
[supervisor  ] service 'nginx' exited (with status 0).
[supervisor  ] stopping service 'xvnc'...
[xvnc        ] Thu Aug  1 16:03:55 2024
[xvnc        ]  ComparingUpdateTracker: 0 pixels in / 0 pixels out
[xvnc        ]  ComparingUpdateTracker: (1:-nan ratio)
[supervisor  ] service 'xvnc' exited (with status 0).
[finish      ] executing container finish scripts...
[finish      ] all container finish scripts executed.

[jlesage]

No it should not. According to the provided log, the container has been requested to shutdown:

[supervisor  ] SIGTERM received, shutting down...

[imsorrywhat]

would supervisor be the OS? this is the only container out of 16 that it happens to. Ubuntu 22.04.04 LTS VM that is only used for Docker.

[jlesage]

The supervisor from the log is a process running inside the container. It receives a SIGTERM signal when the container is stopped.

[imsorrywhat]

Thanks for the assist. Got the bottom of it. Didn't have a restart policy applied so container was not being restarted on reboots. Since I don't use it daily I didn't notice it right away so it seemed like it was a random stop.

Fix: added "restart: always" to docker-compose file, aka Stack in Portainer.