manrw

I used the slskd guides to create the app. I'm happy to adjust the app template if you figure out that there is an issue with it. But I don't see any at the moment. Sorry that I can't help, I am not contributing to slskd - I just made the template.

Also have a look at https://github.com/slskd/slskd/issues/1554

@Tpole this is not a slskd issue and it's not caused by my template. Please see https://forums.unraid.net/topic/112611-no-such-container-message-after-restart/

Glad you got it working. @Jokerigno can you also check this?

Thanks for checking. Just to confirm, your file system is not out of space, correct? Can you read and check the issues here? GitHubslskd/slskdA modern client-server application for the Soulseek file sharing network. - slskd/slskdThe problem is that I'm not using this template myself at the moment and cannot reproduce it either. The "app" is just a docker template of this image. If we cannot figure it out, we will need to submit an issue there. I'm not involved in the development of slskd. Can you let me know if any of the troubleshooting steps or fixes in those issues fixed it? Oh and what else is there to select in "Access mode"? Is there one permission level higher? Perhaps slskd needs execute too?

Thanks for the comment. I checked whether there were any breaking changes in recent releases, but I could find any: https://github.com/slskd/slskd/releases Looking at the template I made for slskd, it targets the persistence directory /app correctly. Do you also get "exists, but is not writeable"? If yes, can you chown or chmod the directories? Can you try mounting /incomplete and /downloads? Perhaps the file system is read-only when un-mounted and slskd will not work due to it being unwriteable?

Hi, when adding integrations, it is important that Homarr can establish a network connection with your targets. Please check out our guide at https://homarr.dev/docs/next/management/integrations/#troubleshooting-connection to troubleshoot.

Danke für die Antwort. Ja, es gibt eine komplett neue Version. Unraid aktualisiert leider Templates nicht direkt, sondern nur das dazugehörige Docker Image - bedeutet also du hast deshalb noch nichts davon mitbekommen. Eine Migration von 0.15.10 ist möglich, aber du musst dazu unsere Englische Anleitung befolgen: https://homarr.dev/blog/2025/01/19/migration-guide-1.0 Falls du das default.json noch lokal hast, kannst du manuell eine neue Instanz von der alten Version starten, indem du einen custom container erstellst und das alte Image verwendest. Dann kannst du die Schritte in der Anleitung verfolgen. Falls dir das zu kompliziert ist, dann kannst du natürlich auch neu starten und die Chance nutzen, gleich etwas aufzuräumen. In der neuen Version gibt es viele neue Features, ein neues Design und vieles mehr. Den Befehl zum ersten vom Schlüssel kannst du übrigens auf irgendeinem Linux System ausführen - am besten brauchst du gleich dein Unraid dazu. Öffne einfach die Konsole oder eine SSH Verbindung zu deinem Unraid Host und führe den Befehl dort aus. Anschliessend kannst du das Ergebnis vom Befehl in das Homarr Template kopieren. LG

Danke. Wie hast du dein Verschlüsselungs Key erstellt? Er ist im falschen Format. Wenn du die Texte im Template gut durchliest, dann steht dort wie du wen genau erstellen musst. Falls du vorher Homarr bereits am laufen hattest, dann verwende bitte den Key von damals, da dieser zum Speichern und Lesen von den Integrationen gebraucht wird. Wenn du ihn nachträglich änderst, musst du alle Passwörter und Tokens in den Integrationen neu eingeben. Wir tun dies aus Sicherheitsgründen und um deine Daten zu schützen. LG

Thanks for the update. I'm happy to update the template once someone has figured out a solution. Thanks for your work so far @jademonkee

Hi @moonsorrox, ich bin einer der Homarr Entwickler. Kannst du mal deine Logs posten? Dann kann ich dir besser helfen, falls das Problem bei Homarr liegt. Danke 👍

Hi, sorry for the late reply. What you did is correct. You can contribute the change here: https://github.com/manuel-rw/unraid-templates

Hi, first this support thread is no longer the correct one. Use Regarding Homarr, please post your log. Homarr 1.0 is a huge rewrite of the application and there are lots of breaking changes that you must read beforehand: https://homarr.dev/blog/2025/01/19/migration-guide-1.0

Hi @strykar_wolf, please report the issue to the GitHub repository. Thank you

Hallo, ich bin der Entwickler von Homarr und helfe dir gerne weiter. Homarr unterstützt das Starten, Stoppen und Löschen von Container per UI. Dies ist hier dokumentiert: https://homarr.dev/docs/advanced/configuration/environment-variables#docker-integration Du kannst diese Funktionalität deaktivieren, wenn du die nicht möchtest, indem du in deiner Unraid App den Mount zu /var/run/docker.sock löscht. Dadurch ist es nicht länger möglich Container zu stoppen oder löschen. Bezüglich Sicherheit: deine Container sehen per Standard immer dein Netzwerk. Möchtest du zusätzlich Sicherheit dann empfehle ich die benutzerdefinierte Docker Netzwerke oder VLANs. LG

Just ensure to put a space between options like you do on Linux commands: --optionA valueA --optionB valueB In your case, that would probably be something along the lines of --network mycontainer --user ???:???

Hi, you can add the user flag in the "Extra argugments" when editing the docker container. You may need to activate the advanced mode if you do not see this field. Please do not ask the image authors for Unraid specific questions, because they usually will not know how Unraid works. Setting 777 will work but is strongly not recommended, because it will enable anyone on the machine to write, read, delete and execute these specific files. This is considered to be dangerous because this could be used in a malicious way and is therefore considered bad practice.

Dashdot should not need any persistence on the file system. The default set-up should work. Can you explain why you want to mount? If you want to mount the container, you can do this by editing the container.

Hi, this is not an issue with the template: https://forums.unraid.net/topic/141336-cant-pull-or-update-docker-containers-dns-issue/

Sounds good 👍. If you still have any trouble after that I would suggest that you open an slskd issue.

Hi, I'd like to emphasize that I'm not the image author but only created the template. This means I generally can't help with any modifications that do not exist in my default template that I provide. That being said, I think you have multiple options to fix the container permissions: Ensure that the directories are owned by the docker user. This is usually "nobody". You can also add this user to a group on your host machine and permit write & read to this user. The application shouldn't need execute. It seems that the container runs on root via default: https://github.com/slskd/slskd/blob/master/docs/docker.md . You could ensure that root can write & read on these directories. In the worst case, you could permit all users to write & read. This is considered bad practice and is not recommended. However, it might not be too bad if no parts of your server are exposed. If you still have trouble, I would suggest reaching out to the author of slskd. Keep in mind that they usually don't know "Unraid" or other distributions and they expect you to provide the docker run command (you can obtain this from Unraid). I hope this helps.

Hi, you need to have a list instead of a single string: https://github.com/slskd/slskd/blob/master/docs/config.md#directories. shares: directories: - "/musique"

Hi, I recommend you to read the configuration for the shared: https://github.com/slskd/slskd/blob/master/docs/config.md#shares . Please note that you must mount your directories to inside the container using a path mode (prefer read-only if possible). Then reference this path using the config. So when you're editing the config file, you're unable to edit it? Have you read https://github.com/slskd/slskd/blob/master/docs/docker.md ? As far as I can see, you should edit this on the mounted directory while the application is stopped, save it and then restart the application.

You'll see an update button in Unraid when it get's updated. We publish updates here and you can subscribe on the repository to get notified by GitHub for new releases: https://github.com/ajnart/homarr/releases

Hi, Dash. does not offer any mount points: https://getdashdot.com/. This is why you don't see any in Unraid.