@grtgbln please can you add the following variables to your SparkyFitness---Frontend docker template, they are missing and cause the docker to fail starting. Thanks

SPARKY_FITNESS_FRONTEND_URL: ${SPARKY_FITNESS_FRONTEND_URL}

SPARKY_FITNESS_SERVER_HOST: sparkyfitness-server # Internal Docker service name for the backend

SPARKY_FITNESS_SERVER_PORT: 3010 # Port the backend server listens on

Hey, just went through the work to set this up on Unraid, and found that either the app had not been updated in some time or perhaps I was doing something wrong.

• it did not update to later versions of :master, since the repo did not include "docker.io/" as well it was lacking the Navidrome URL.

Either way I decided to submit this in case it helps to update the Unraid App for users like me.
If this is not helpful, feel free to just ignore it and move on.

Text form:

Repository: docker.io/docccccc/soulbeet:master

Network Type: Bridge

Use Tailscale: Off

Console shell command: Shell

Privileged: Off

Web UI Port: 9765

Secret Key: RANDOM_STRING

Soulseek - URL: http://IP_ADDRESS:5030

Soulseek - API Key: (I think this is just a holdover from a previous version and could be removed)

Soulseek - Internal Download Folder: /downloads

Beets - Music Folder: /mnt/user/media/music/

Navidrome URL: http://IP_ADDRESS:4533

Soulseek - External Download Folder: /mnt/user/media/music/downloads/

Data Folder: /mnt/user/appdata/soulbeet/data

Database URL: sqlite:/data/soulbeet.db

The Pinepods template should be updated to include that it requires Valkey plus a few environmental variables:

VALKEY_HOST: valkey

VALKEY_PORT: 6379

Any suggestions on how to get TinyAuth v.5 working? It have major changes in configuration files for version 5.x that breaks TinyAuth if updating.
Had to go back to 4.1, latest need some modifications.

9 hours ago, JOG said:

Any suggestions on how to get TinyAuth v.5 working? It have major changes in configuration files for version 5.x that breaks TinyAuth if updating.
Had to go back to 4.1, latest need some modifications.

I don't see any documented changes in terms of Docker container setup for v5. Issues with the config or anything inside the container are best directed at the upstream developer: https://github.com/steveiliop56/tinyauth/issues?q=sort%3Aupdated-desc%20is%3Aissue%20is%3Aopen

The environmental variables has changed according to the documentation. I did a post about it if it may help https://gill.nu/2026/04/10/unraid-tinyauth-v5-migration/
May be some better way to do it but it works.

7 hours ago, JOG said:

The environmental variables has changed according to the documentation. I did a post about it if it may help https://gill.nu/2026/04/10/unraid-tinyauth-v5-migration/
May be some better way to do it but it works.

Reading at https://forums.unraid.net/topic/133764-support-grtgbln-docker-templates/page/14/ the unraid repository owner grtgbln had made an answer on the issues: “I don’t see any documented changes in terms of Docker container setup for v5. Issues with the config or anything inside the container are best directed at the upstream developer: https://github.com/steveiliop56/tinyauth/issues?q=sort%3Aupdated-desc%20is%3Aissue%20is%3Aopen“.

I continued reading documentation at https://tinyauth.app and it clearly states that the Enviromental Variables has completely changed in v5.

I therefore do not agree with grtgbln’s answer on the issue and this is why this post were made.

Little friendly advice man, when you think someone is mistaken, it's a lot nicer to kindly point them in the right direction rather than putting them on blast in a blog post.

My automated monitoring system relies on the app developers updating certain files, typically Docker Compose files, which hasn't been updated for TinyAuth. I was not monitoring their documentation files.

Looking at the changes now.

jo @grtgbln ,
the BrickTracker Unraid template seems outdated and doesn’t really work anymore with the newer versions.
Since v1.3 there were some breaking changes, so the current template setup doesn’t fit anymore.
Would be great if you could update it.
Mirgation Guide
Thanks 👍

Hello, I was looking at using the "Obsidian-LiveSync-CouchDB" template and just wanted to note that there should be an additional path added to the template:

On the original GH page, teh compose has it but not the default docker line:

    volumes:
      - ${COUCHDB_DATA}:/opt/couchdb/data

Trying to setup SparkyFitness. I have the frontend setup, which starts fine, and I can load up the login screen(it does show an error popup in the bottom right, since there is no backend to connect to). I was already running Postgres 15, so I manually created a database and user, and setup all of the permissions and extensions and whatnot as per the SparkyFitness docs. But the backend will not start. I just get:

Failed to start server: Error: getaddrinfo ENOTFOUND http://192.168.0.215

at /app/SparkyFitnessServer/node_modules/.pnpm/[email protected][email protected]/node_modules/pg-pool/index.js:45:11

at process.processTicksAndRejections (node:internal/process/task_queues:104:5)

at async getSystemClient (/app/SparkyFitnessServer/db/poolManager.ts:76:18)

at async applyMigrations (/app/SparkyFitnessServer/utils/dbMigrations.ts:12:18) {

errno: -3008,

code: 'ENOTFOUND',

syscall: 'getaddrinfo',

hostname: 'http://192.168.0.215'

}

edit* Nevermind, I solved it myself. Couldn't get this working no matter what I tried. Ended up installing Portainer from the Community Apps, using Portainer to setup the SparkyFitness stack per their instructions, which worked perfectly right away, and then used all of the environment variables and other settings from that to manually recreate those container templates in Unraid's Docker system so they can be managed like everything else, without having to keep Portainer (though I might keep it available anyway, since it's useful).

Edited May 26May 26 by Zhono
solved it myself

On 5/17/2026 at 5:43 PM, martial said:

Hello, I was looking at using the "Obsidian-LiveSync-CouchDB" template and just wanted to note that there should be an additional path added to the template:

On the original GH page, teh compose has it but not the default docker line:

    volumes:
      - ${COUCHDB_DATA}:/opt/couchdb/data

Thanks for the heads up, updated

Edited May 26May 26 by [email protected]

The Unraid docker container template for LocalAI is out of date for the path variables to ensure persistent storage. Even though LocalAI is listed as "official" in the app store it doesn't have the correct paths. I had to go to the localai documentation to figure out what the path variables were so it didn't erase my data when updating. Anyway to get that updated?

2 hours ago, axsdenied said:

The Unraid docker container template for LocalAI is out of date for the path variables to ensure persistent storage. Even though LocalAI is listed as "official" in the app store it doesn't have the correct paths. I had to go to the localai documentation to figure out what the path variables were so it didn't erase my data when updating. Anyway to get that updated?

Updated, thanks for the heads up.

Mousehole need a variable update

On 2/15/2025 at 12:05 PM, csb said:

I'm pretty sure the Libation template is currently incompatible with the semi-recent "breaking changes" made to its Docker:

 

https://github.com/rmcrackan/Libation/blob/master/Documentation/Docker.md

 

I believe it runs as the wrong user and group (should run as 99:100 on Unraid, but runs as 1001:1001).

 

"-u 99:100" under extra parameters fixes it, somewhat ... the UMASK is still wrong and written files can't be edited via SMB. No idea how to fix UMASK, though.

@csb did you ever figure this out? Im going insane trying to figure out the UMASK issue.

Hi, I recently installed Webtrees and am getting this error. I installed 2 different Maria SQL dockers and the Mysql one thinking it was an issue on that end. I was eventually able to get Webtrees up by mapping the database to a docker IP for the container running the SQL. Well I rebooted and that IP changed so I switched it to the newer docker IP and now get this again. Ive tried My server IP, the Docker IP, Localhost, 127.0.0.1. Ive changed ports. Im not sure where to roceed. Thanks

RuntimeException: SQLSTATE[HY000] [2002] Connection refused in /var/www/html/app/DB.php:141