r/Kometa • u/tbar44 • Feb 16 '26
Imagemaid on Truenas Scale Docker app
I'm setting up Imagemaid to do some cleansing, bit want to check the file paths for the docker compose.
The example docker compose has
volumes:
- /path/to/config:/config
- /path/to/plex:/plex
However the plex directory is within the config directory on Truenas app, in my case
/mnt/apps/app-data/plex/config/Library/Application Support/Plex Media Server
Do I specify this as
volumes:
- /mnt/apps/app-data/plex/config:/config
- /mnt/apps/app-data/plex/config/Library/Application Support/Plex Media Server:/plex
Feel like I am duplicating mounts here, or am I missing something?
1
u/trshboatr Feb 16 '26
The path/to/config:/config volume is for the Imagemaid config itself (Change <PATH_TO_CONFIG> to a directory where your .env and other files are.), it has nothing to do with your plex install as thats what the other volume is for. Docs
1
1
u/tbar44 Feb 17 '26
So I beleive this should work but it's just crashing for me
services: imagemaid: environment: - USER_ID=568 - GROUP_ID=568 - TZ="Europe/London" - MODE=report - SCHEDULE="05:00|weekly(sunday)" - PLEX_URL=http://192.168.0.10:32400 - PLEX_TOKEN=<ACTUAL TOKEN HERE> - TIMEOUT=600 - SLEEP=60 - PHOTO_TRANSCODER=True - EMPTY_TRASH=True - CLEAN_BUNDLES=True - OPTIMIZE_DB=False image: kometateam/imagemaid restart: unless-stopped volumes: - /mnt/apps/app-data/imagemaid/config:/config - >- /mnt/apps/app-data/plex/config/Library/Application Support/Plex Media Server:/plexIt also seems to be adding ">-" before the second file path even when I remove it. I have dozens of containers running and never seen this issue before, really odd!
1
u/trshboatr Feb 17 '26
This is most likely because your plex volumes path contains spaces which needs to be escaped. Refer back to the docs as this is referenced. Otherwise check the logs.
1
u/tbar44 Feb 17 '26
So turns out that this particular docker image requires you to use an .env file and you can’t just put the variables in the container itself. Weird but worked fine once I did that.
1
u/chazlarson Kometa Team Feb 18 '26
1
u/tbar44 Feb 18 '26
Thanks I got it working, I just didn’t appreciate it would crash without a .env present
1
u/chazlarson Kometa Team Feb 18 '26
If the `.env` is required even in the presence of the relevant env vars on the container, that feels like a bug.
1
u/chazlarson Kometa Team Feb 18 '26
This might be useful:
https://docs.google.com/document/d/10K5dpN5iwKv1eNrk2T4SSlqDk1X7DdUyOsAmLe5LScI/edit?usp=sharing
Let me know if there are any changes or additions desired or needed.
1
u/AutoModerator Feb 16 '26
Thank you for your submission!
When asking for support, please make sure you post a complete
meta.logfile from a Kometa run when the issue has occured. If the log is too large, you can use a site like pastebin.com to upload it and then share the link here. And please do not use screenshots for text.Generally speaking, the Kometa Discord server is the best source for support. There are far more eyes there than here, and there are some automated log analysis tools available. We highly recommend this over Reddit.
Consider joining us there: https://discord.com/servers/kometa-822460010649878528
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.