Whenever custom container updates, config is lost?

Apps and Virtualization
1

I have bunch of containers added via compose yaml. Whenever there is update, they loose their configs(or attleast most of them)… I suppose this is not normal? I see that jackett container has now update available, if needed and instructed. i could take logs or something when updating.

Or is this example container configuration faulty somehow:

services:
  pinchflat:
    environment:
      - TZ=Europe/Helsinki
    image: ghcr.io/kieraneglin/pinchflat:latest
    ports:
      - '8945:8945'
    volumes:
      - /mnt/container/pinchflat/config:/config
      - /mnt/media/media/Youtube:/downloads

Whats mindbogling, is for example qbittorrentvpn custom container deletes vpn files when upgrading ? For me it looks like whole folder where container resides, is renewed?

2

You might want to add uid/gid to your compose and make sure those have RW permissions for those datasets.

services:
  qbittorrent:
    container_name: qbittorrent
    environment:
      - PUID=568
      - PGID=568
      - TZ=****
      - WEBUI_PORT=10095
      - TORRENTING_PORT=6881
      - UMASK=022
    image: lscr.io/linuxserver/qbittorrent:latest
    network_mode: container:gluetun
    restart: unless-stopped
    volumes:
      - /mnt/APPS/AppData/qbittorrent:/config
      - /mnt/Array1/downloads/torrents:/mnt/Array1/downloads/torrents

Scale’s built in app:app is 658:658.

1 Like