Install with Portainer on Docker
Installing on Ubuntu with Portainer as a 'stack' (Compose)
Not finding audiobook tag, and not listing audiable as a source.
output of beet
root@04f73e0003e1:/# beet --version
beets version 1.6.0
Python version 3.10.12
plugins: chroma, convert, embedart, fetchart, lastgenre, replaygain, scrub, web
root@04f73e0003e1:/#
Directory
.
├── config
│ ├── beets.sh
│ ├── config.yaml
│ └── musiclibrary.blb
├── docker-compose.yml
└── scripts
└── install-deps.sh
compose
version: "3"
services:
beets:
image: lscr.io/linuxserver/beets:1.6.0-ls180
container_name: beets
environment:
# Update as needed
- PUID=1000
- PGID=100
- TZ=America/New_York
volumes:
- /mnt/data/docker/config/beets/config:/config
- /mnt/data/docker/config/beets/scripts:/custom-cont-init.d
- /mnt/data/NAS2/audiobooks/done:/audiobooks
- /mnt/data/NAS2/audiobook/untagged:/input
**log**
Brought to you by linuxserver.io
───────────────────────────────────────
To support LSIO projects visit:
https://www.linuxserver.io/donate/
───────────────────────────────────────
GID/UID
───────────────────────────────────────
User UID: 1000
User GID: 100
───────────────────────────────────────
[custom-init] Files found, executing
[custom-init] install-deps.sh: executing...
Installing dependencies...
Requirement already satisfied: beets-audible in /usr/lib/python3.10/site-packages (0.1.0)
Requirement already satisfied: beets-copyartifacts3 in /usr/lib/python3.10/site-packages (0.1.5)
Requirement already satisfied: markdownify==0.11.6 in /usr/lib/python3.10/site-packages (from beets-audible) (0.11.6)
Requirement already satisfied: natsort==8.2.0 in /usr/lib/python3.10/site-packages (from beets-audible) (8.2.0)
Requirement already satisfied: beautifulsoup4<5,>=4.9 in /usr/lib/python3.10/site-packages (from markdownify==0.11.6->beets-audible) (4.12.2)
Requirement already satisfied: six<2,>=1.15 in /usr/lib/python3.10/site-packages (from markdownify==0.11.6->beets-audible) (1.16.0)
Requirement already satisfied: beets>=1.3.11 in /usr/lib/python3.10/site-packages (from beets-copyartifacts3) (1.6.0)
Requirement already satisfied: unidecode in /usr/lib/python3.10/site-packages (from beets>=1.3.11->beets-copyartifacts3) (1.3.6)
Requirement already satisfied: musicbrainzngs>=0.4 in /usr/lib/python3.10/site-packages (from beets>=1.3.11->beets-copyartifacts3) (0.7.1)
Requirement already satisfied: pyyaml in /usr/lib/python3.10/site-packages (from beets>=1.3.11->beets-copyartifacts3) (6.0.1)
Requirement already satisfied: mediafile>=0.2.0 in /usr/lib/python3.10/site-packages (from beets>=1.3.11->beets-copyartifacts3) (0.12.0)
Requirement already satisfied: confuse>=1.0.0 in /usr/lib/python3.10/site-packages (from beets>=1.3.11->beets-copyartifacts3) (2.0.1)
Requirement already satisfied: munkres>=1.0.0 in /usr/lib/python3.10/site-packages (from beets>=1.3.11->beets-copyartifacts3) (1.1.4)
Requirement already satisfied: jellyfish in /usr/lib/python3.10/site-packages (from beets>=1.3.11->beets-copyartifacts3) (1.0.0)
Requirement already satisfied: soupsieve>1.2 in /usr/lib/python3.10/site-packages (from beautifulsoup4<5,>=4.9->markdownify==0.11.6->beets-audible) (2.4.1)
Requirement already satisfied: mutagen>=1.46 in /usr/lib/python3.10/site-packages (from mediafile>=0.2.0->beets>=1.3.11->beets-copyartifacts3) (1.46.0)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
[notice] A new release of pip is available: 23.2.1 -> 24.0
[notice] To update, run: pip install --upgrade pip
[custom-init] install-deps.sh: exited 0
* Serving Flask app 'beetsplug.web'
* Debug mode: off
WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
* Running on all addresses (0.0.0.0)
* Running on http://127.0.0.1:8337
* Running on http://172.22.0.2:8337
Press CTRL+C to quit
[ls.io-init] done.
Can you exec into the container and check that the Beets config file is mapped into the container correctly?
Can you exec into the container
YES
and check that the Beets config file is mapped into the container correctly?
Need guidance on how to check that.
I did some reading on beet and I do not think I have the config ??
beet config
I completely missed Step 5 - "Update the config in config/config.yaml as described above."
I completely missed Step 5 - "Update the config in config/config.yaml as described above."
Did this resolve the issue?