[BUG] <Docker container exiting itself>

[ddidjeira]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

I have a weird behavior of my container for a few months.

After some time the container is exiting itself and on the docker logs i have a "Catching signal: SIGTERM"

I started the service at 22:03 (10:03 PM), the added a torrent à 22h23 (10:23 PM) . The download was completed at 22h26 (10:26PM)

bellow the logs

Expected Behavior

No response

Steps To Reproduce

Don't know how to reproduce myself

Environment

- OS: Ubuntu 22.04.4 LTS
- Docker is installed in swarm mode with 4 nodes and I have a constraint that keeps qbittorrent container on the same node. It's the only container on the node except the portainer agent container

CPU architecture

x86-64

Docker creation

---
version: "3.7"
services:
  qbittorrent:
    image: lscr.io/linuxserver/qbittorrent:latest
    environment:
      - PUID=1010
      - PGID=1010
      - TZ=Europe/Paris
      - DELUGE_LOGLEVEL=error #optional
      - WEBUI_PORT=8199
    volumes:
      - /cephfs/docker/qbittorrent/config:/config
      - /syno:/downloads
    ports:
      - 50127:50127   #PIAVPN
      - 1337:1337
      - 8199:8199
      - 6881:6881
    networks:
      - allcontainers
    deploy:
      mode: replicated
      replicas: 1
      restart_policy:
        condition: none
      placement:
        constraints:
          - node.labels.deployable == yes
          - node.labels.runqbittorrent == yes

networks:
  allcontainers:
    external: true

Container logs

2024-11-01T22:03:14.963001625Z qbittorrent_qbittorrent.1.hqnfq8k2tgw6@docker2    | [migrations] started
2024-11-01T22:03:14.963080001Z qbittorrent_qbittorrent.1.hqnfq8k2tgw6@docker2    | [migrations] no migrations found
2024-11-01T22:03:15.082760345Z qbittorrent_qbittorrent.1.hqnfq8k2tgw6@docker2    | ───────────────────────────────────────
2024-11-01T22:03:15.082774345Z qbittorrent_qbittorrent.1.hqnfq8k2tgw6@docker2    |
2024-11-01T22:03:15.082777517Z qbittorrent_qbittorrent.1.hqnfq8k2tgw6@docker2    |       ██╗     ███████╗██╗ ██████╗
2024-11-01T22:03:15.082780125Z qbittorrent_qbittorrent.1.hqnfq8k2tgw6@docker2    |       ██║     ██╔════╝██║██╔═══██╗
2024-11-01T22:03:15.082782597Z qbittorrent_qbittorrent.1.hqnfq8k2tgw6@docker2    |       ██║     ███████╗██║██║   ██║
2024-11-01T22:03:15.082786251Z qbittorrent_qbittorrent.1.hqnfq8k2tgw6@docker2    |       ██║     ╚════██║██║██║   ██║
2024-11-01T22:03:15.082788658Z qbittorrent_qbittorrent.1.hqnfq8k2tgw6@docker2    |       ███████╗███████║██║╚██████╔╝
2024-11-01T22:03:15.082791220Z qbittorrent_qbittorrent.1.hqnfq8k2tgw6@docker2    |       ╚══════╝╚══════╝╚═╝ ╚═════╝
2024-11-01T22:03:15.082793615Z qbittorrent_qbittorrent.1.hqnfq8k2tgw6@docker2    |
2024-11-01T22:03:15.082801166Z qbittorrent_qbittorrent.1.hqnfq8k2tgw6@docker2    |    Brought to you by linuxserver.io
2024-11-01T22:03:15.082803772Z qbittorrent_qbittorrent.1.hqnfq8k2tgw6@docker2    | ───────────────────────────────────────
2024-11-01T22:03:15.082806210Z qbittorrent_qbittorrent.1.hqnfq8k2tgw6@docker2    |
2024-11-01T22:03:15.082808478Z qbittorrent_qbittorrent.1.hqnfq8k2tgw6@docker2    | To support LSIO projects visit:
2024-11-01T22:03:15.082810813Z qbittorrent_qbittorrent.1.hqnfq8k2tgw6@docker2    | https://www.linuxserver.io/donate/
2024-11-01T22:03:15.082813057Z qbittorrent_qbittorrent.1.hqnfq8k2tgw6@docker2    |
2024-11-01T22:03:15.082815309Z qbittorrent_qbittorrent.1.hqnfq8k2tgw6@docker2    | ───────────────────────────────────────
2024-11-01T22:03:15.082817734Z qbittorrent_qbittorrent.1.hqnfq8k2tgw6@docker2    | GID/UID
2024-11-01T22:03:15.082819988Z qbittorrent_qbittorrent.1.hqnfq8k2tgw6@docker2    | ───────────────────────────────────────
2024-11-01T22:03:15.085317614Z qbittorrent_qbittorrent.1.hqnfq8k2tgw6@docker2    |
2024-11-01T22:03:15.085324919Z qbittorrent_qbittorrent.1.hqnfq8k2tgw6@docker2    | User UID:    1010
2024-11-01T22:03:15.085327845Z qbittorrent_qbittorrent.1.hqnfq8k2tgw6@docker2    | User GID:    1010
2024-11-01T22:03:15.085330352Z qbittorrent_qbittorrent.1.hqnfq8k2tgw6@docker2    | ───────────────────────────────────────
2024-11-01T22:03:15.086195337Z qbittorrent_qbittorrent.1.hqnfq8k2tgw6@docker2    | Linuxserver.io version: 5.0.0-r2-ls361
2024-11-01T22:03:15.086522902Z qbittorrent_qbittorrent.1.hqnfq8k2tgw6@docker2    | Build-date: 2024-10-27T06:52:25+00:00
2024-11-01T22:03:15.086529421Z qbittorrent_qbittorrent.1.hqnfq8k2tgw6@docker2    | ───────────────────────────────────────
2024-11-01T22:03:15.086532549Z qbittorrent_qbittorrent.1.hqnfq8k2tgw6@docker2    |
2024-11-01T22:03:15.247494581Z qbittorrent_qbittorrent.1.hqnfq8k2tgw6@docker2    | [custom-init] No custom files found, skipping...
2024-11-01T22:03:15.395510993Z qbittorrent_qbittorrent.1.hqnfq8k2tgw6@docker2    | WebUI will be started shortly after internal preparations. Please wait...
2024-11-01T22:03:15.999077292Z qbittorrent_qbittorrent.1.hqnfq8k2tgw6@docker2    |
2024-11-01T22:03:15.999093346Z qbittorrent_qbittorrent.1.hqnfq8k2tgw6@docker2    | ******** Information ********
2024-11-01T22:03:15.999096654Z qbittorrent_qbittorrent.1.hqnfq8k2tgw6@docker2    | To control qBittorrent, access the WebUI at: http://localhost:8199
2024-11-01T22:03:16.284692720Z qbittorrent_qbittorrent.1.hqnfq8k2tgw6@docker2    | Connection to localhost (::1) 8199 port [tcp/*] succeeded!
2024-11-01T22:03:16.292676395Z qbittorrent_qbittorrent.1.hqnfq8k2tgw6@docker2    | [ls.io-init] done.
2024-11-03T23:04:27.050595273Z qbittorrent_qbittorrent.1.hqnfq8k2tgw6@docker2    | Catching signal: SIGTERM
2024-11-03T23:04:27.051126177Z qbittorrent_qbittorrent.1.hqnfq8k2tgw6@docker2    | Exiting cleanly

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[aptalca]

The container is receiving a docker stop from the outside. Likely your swarm instance is set up to stop/restart containers based on a healthcheck that doesn't exist here.

[ddidjeira]

hmm. I haven't made any specific configurations in Swarm to stop or start containers. Could this be caused by Portainer?
for the record that's the only container doing this.

[j0nnymoe]

No one within the team uses portainer and we don't recommend/support it.

[ddidjeira]

okay thanks. i will try on a standalone docker

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.