You don't actually need those variables set to run the container. You can set them in the WebUI.

The log confused me the first time too. There is no indication that it has finished starting up, but if you go to the WebUI, it should be there.

1 hour ago, JPDVM2014 said:

You don't actually need those variables set to run the container. You can set them in the WebUI.

The log confused me the first time too. There is no indication that it has finished starting up, but if you go to the WebUI, it should be there.

I now Realize this was due to me picking a bad port (5060) because the 5055 was already in use on my server. All is working correctly now. Sorry for the confusion, and Thanks for your help!

File "/python/fastapi/routing.py", line 134, in merged_lifespan

async with original_context(app) as maybe_original_state:

File "/usr/lib/python3.11/contextlib.py", line 204, in aenter

return await anext(self.gen)

^^^^^^^^^^^^^^^^^^^^^

File "/app/app.py", line 188, in lifespan

setup_logging()

File "/app/app.py", line 86, in setup_logging

p.mkdir(parents=True, exist_ok=True)

File "/usr/lib/python3.11/pathlib.py", line 1117, in mkdir

os.mkdir(self, mode)

PermissionError: [Errno 13] Permission denied: 'logs/tasks'

Getting this error from Spotizerr, any ideas?

Did you run this in your terminal before starting? You need to adjust this command to wherever your appdata folder is, if it is different. And change the 99:100 part to match whatever you are running spotizerr as. If you left the template default, then this command should work as-is.

"mkdir -p /mnt/user/appdata/spotizerr-phoenix && touch /mnt/user/appdata/spotizerr-phoenix/.cache && chown -R 99:100 /mnt/user/appdata/spotizerr-phoenix"

You might have to delete a .cache directory if it exists. If you run the container without creating the .config file, it usually creates it as a directory instead.

Edited January 6Jan 6 by JPDVM2014

I am able to run the container now, but I can't access the container console to use the auth tool

root@Apollo:~# docker exec -it spotizerr-phoenix sh

OCI runtime exec failed: exec failed: unable to start container process: exec: "sh": executable file not found in $PATH: unknown

root@Apollo:~# docker run --rm -ti spotizerr-phoenix sh

Unable to find image 'spotizerr-phoenix:latest' locally

docker: Error response from daemon: pull access denied for spotizerr-phoenix, repository does not exist or may require 'docker login': denied: requested access to the resource is denied.

See 'docker run --help'.

This is what I'm getting now

Edited January 6Jan 6 by CopesaCola

You can run "docker run --network=host --rm -it cooldockerizer93/spotizerr-auth" to get the auth tool.

Sooooo.... did the Ephemera project disappear or did the dev just change names? Seems like the developer OrwelianEpilogue had commits to bannert1337/ephemera back in November/December, but the project is gone from the original repo.

I guess I'm switching to Shelfmark (formerly Calibre Web Advanced Downloader).

Edited January 14Jan 14 by ignitionnight

Yea, looks like it is gone. That's a shame, it was more reliable for me than CWABD. Guess I'll go back too and give it a try again.

There's something wrong with the 'Listenarr' docker image. Installed with defaults (set path to existing Audiobooks library) but the WebUI never starts / is inaccessible.

Checked the logs for the container and this pops up in the log:

npm error syscall mkdir

npm error path /.npm

npm error errno EACCES

npm error

npm error Your cache folder contains root-owned files, due to a bug in

npm error previous versions of npm which has since been addressed.

npm error

npm error To permanently fix this problem, please run:

npm error sudo chown -R 99:100 "/.npm"

npm error Log files were not written due to an error writing to the directory: /.npm/_logs

npm error You can rerun the command with --loglevel=verbose to see the logs in your terminal

The Daemon appears to be running when monitoring the logs, but no WebUI on port 5000.

Dan / Gib.

EDIT: Apparently, the Listenarr app now uses port 4545 and NOT port 5000 (version update / change) so the docker image template will need to be updated to reflect this.

Edited January 16Jan 16 by GibsonXXI

Thanks, I'll update it!

12 minutes ago, JPDVM2014 said:

Thanks, I'll update it!

Thanks JPDVM2014.

You might also want to add a default folder mapping for the 'Download' folder as well. I can't speak for others who use the 'arr' apps, but I have a dedicated share for Downloaded files which is separate to the share on which the media library resides. Adding such a mapping manually isn't difficult, but might save some time for the less container-savvy users who might want to use the Listenarr docker image you provided.

🙂

Dan / Gib.

Good idea. I just committed the changes. Will be in the CA store next time it updates.

On 1/17/2026 at 12:43 AM, JPDVM2014 said:

Good idea. I just committed the changes. Will be in the CA store next time it updates.

I've got CA Auto-update plugin set to daily (1am). Not been sent any prompt to update Listenarr. When is the CA repo likely to see and reflect your changes? I was hoping to get this set up before the end of the weekend, ideally (Sorry if this sounds pushy).

Dan / Gib.

My template changes don't actually update the container, so it wouldn't be caught by the auto-update plugin. You'll have to install it again from the CA store.

Edited January 18Jan 18 by JPDVM2014

8 hours ago, JPDVM2014 said:

My template changes don't actually update the container, so it wouldn't be caught by the auto-update plugin. You'll have to install it again from the CA store.

Of course not, it's not a core code change, forgot this fact. Thanks for the clarification.

Dan / Gib.

No problem! Let me know if you run into any issues with it. I've got it up and running on my system with the changes.

Edited January 19Jan 19 by JPDVM2014

I'm still getting the same issue, but I am trying to embed it within Binhex's DelugeVPN container for networking. I'll have to remove the port allocation from that add-on and try starting it in bridge mode, separately, and see what happens then. I've run out of time tonight though, so I'll look at it when I get home from work tomorrow.

The error I posted in my first post is also still occurring, and I think the problematic '.npm' folder it complains about has something to do with the Web UI. Actually had this installed since before Xmas, but disabled because I didn't have time to set it up, so put it on the back-burner.

Dan / Gib.

Yea, I'd try getting it at least to load to the WebUI before adding in the VPN. Then get the VPN sorted out before adding any indexers.

Whenever you get a chance, if you want to post a screenshot of your template, I can see if anything stands out.

I get that same npm error, but it doesn't seem to cause any issues. Only related error I see is that it can't write npm logs.

My guess is it is because of the container running as "--user 99:100". You could turn on advanced view and remove that from the Extra Parameters section to see if it helps anything.

If you do remove that, I'd delete your listenarr appdata folder to make sure you are restarting from scratch.

FWIW, I am running with "--user 99:100", and everything seems to be running fine.

Looks like there is an open issue about running as a non-root user.

https://github.com/therobbiedavis/Listenarr/issues/309

So, you'll either have to remove the "--user 99:100" or pre-create the config directory and set correct permissions. If you want to pre-create the config directory, run the below in your unraid terminal. If your appdata is located somewhere other than the default, make sure to change the command to match where it is.

"mkdir /mnt/user/appdata/listenarr/ && chown -R 99:100 /mnt/user/appdata/listenarr/"

I think for ease of use for new installs, I'm going to remove setting the user as part of the template. Anyone who wants/needs to change that should know how.

Edited January 19Jan 19 by JPDVM2014

It turns out the 'appdata' folder created with the first version of Listenarr I installed (i.e: before Xmas) was the root cause for the error posted in the log. I forgot to remove the appdata folder last night when removing & reinstalling it. I went through and completely removed the app and all related templates and appdata folders, and reinstalled it again (30 mins ago at the time of writing).

It's now working fine, have to set it up, enable authentication via the config.json, as it appears that this is disabled by default.

Your post last night that you had it working on your system, JPDVM2014, clued me in to where I may have been going wrong, so thank you for that.

Now to set it up. Should also do Kapowarr too, but I'm waiting for the developer to add Usenet support before I invest any great amount of time in that one.

Enjoy your coffee.

😉

Dan / Gib.

Edited January 19Jan 19 by GibsonXXI

Great, glad you got it working!

PSA: Today I noticed my Docker vDisk was hitting its limit. After some digging, I found that my calibre-web-automated container was the culprit. Further analysis showed that /tmp/calibre was packed with covers and EPUB files, totaling nearly 30 GB! I have no idea how they ended up there.

For safety purposes I recreated the container and passed --tmpfs /tmp:size=2G,mode=1777 as extra parameter.

Thanks for the info! I wonder what caused it. I've got a few hundred books and my /tmp folder is empty.

Maybe it's used during conversion or something and it wasn't cleaning up properly. Hopefully a reinstall fixes it up.

@JPDVM2014 hey, just wanted to let you know that listenarr updated their repo to no longer be a project under the creator. The repo is now under their org “listenarrs” rather than “therobbiedavis”.

There are some big security exploits that they have found recently and fixed but have only been published on their new repo.

The template should now have this as the repo: ghcr.io/listenarrs/listenarr:canary

@Chandler Thanks for letting me know! It should be updated as soon as the CA refreshes.