[BUG] Redundant file structure in /config folder

[vincentkoevoets]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

When starting the container with the following docker-compose.yml, the directory structure seems a bit redundant. There is a /config folder, with inside it another config folder (among others), and inside that yet another config folder. This is output for tree command inside the container /config folder:

/config:
├── backup
├── cache
├── config
│   ├── analytics_visitor_id.txt
│   ├── announcements.json
│   ├── backup
│   ├── cache
│   ├── config
│   │   ├── analytics_visitor_id.txt
│   │   ├── announcements.json
│   │   ├── config.ini
│   │   └── releases.txt
│   ├── config.ini
│   ├── db
│   │   ├── bazarr.db
│   │   ├── bazarr.db-shm
│   │   └── bazarr.db-wal
│   ├── log
│   │   └── bazarr.log
│   ├── releases.txt
│   ├── restore
│   └── throttled_providers.dat
├── db
│   ├── bazarr.db
│   ├── bazarr.db-shm
│   └── bazarr.db-wal
├── log
│   ├── bazarr.log
│   └── bazarr.log.2023-09-10
└── restore

This seems off, because there are several duplicate files and folders present. It could be I'm doing something wrong, but I already removed and recreated the container and the same happens. Also, the mounted volume /home/vincent/.docker/bazarr is not used by the container, nothing is in there after starting the container. I've been using Docker for a long time now, and I use several of your other *arr containers, but this is a first for me.

I'm hoping you can point me in the right direction.

Expected Behavior

The folder structure should be looked at I think, so that we have a nice clean /config folder. Also, the mounted /config folder should be used.

Steps To Reproduce

Run docker compose up -d with the provided docker-compose.yml.

Environment

- OS: Debian 11
- How docker service was installed: came preinstalled

CPU architecture

x86-64

Docker creation

version: "3.3"
services:
  bazarr:
    image: lscr.io/linuxserver/bazarr:latest
    container_name: bazarr
    environment:
      - PUID=1000
      - PGID=1000
      - UMASK=002
      - TZ=Europe/Berlin
    volumes:
      - /home/koevoets/.docker/bazarr:/config
      - /media/ssd/plex/series:/tv
      - /media/ssd/plex/films:/movies
    network_mode: 'service:gluetun' 
    restart: unless-stopped
    profiles: 
      - downloaders

### Container logs

```bash
No logs available.

[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.

[vincentkoevoets]

Wow, I was afraid that it might be something small and stupid, turns out it was. I was trying to mount a non-existent directory into the container (/home/koevoets/.docker/bazarr instead of /home/vincent/.docker/bazarr), and well that gave the unexpected results. Sorry to bother anyone, I will close this now.