Soulseek Dockers

[chem]

Just recently made the jump from Unraid 5 to 6 and am just getting used to Dockers. I've searched quite a bit but can find nothing on getting Soulseek (http://www.soulseekqt.net/news/node/1) to run on Unraid via Dockers. How much of a melt would it be to manually set it up through Dockers?

 

 

[hernandito]

It should not be hard to build based on a Phusion image... I am having a hard time grasping how this works... Is it like your own personal MediaFire or Fileshare, or is it more community share base.

[cirkator]

Soulseek is a peer to peer sharing music program. It is, as far as i know, the most widely used program to share and download music.

Doesn´t have a web interface though, its a standalone program, so it would have to be dockered with the X based docker.

 

 

[mobster909]

I'd really like to have soulseek run on Unraid.

[BBoYTuRBo]

Sorry to revive a zombie thread... but did anyone have any luck with this? I found a soulseek and a nicotine docker that used vnc to allow access, but they're not working correctly.

[ForExampleJohn]

I'm a complete noob with docker, only recently setting up some stuff with it in unraid.  I tried adding danielguerra69's docker and like everyone else couldn't get it to work.  Turns out that the reason is that 32bit apps just don't work properly with docker on unraid - and it's down to unraid's kernel.  The containers I saw were trying to use wine to run a windows soulseek 32bit executable.

 

*However*

 

Soulseek provides a 64bit linux executable.  So, I cloned danielguerra69's project and rebuilt it to use that executable (had to use the nov 2017 beta, feb 2017 crashed all the time).  find the container at whatsalinux/soulseek

 

If you're new with docker as I am, here's the step by step to add it to unraid in docker:

 

1. Click add container
2. name = soulseek
3. repository = whatsalinux/soulseek
4. categories = downloaders
5. Docker Hub URL = https://hub.docker.com/r/whatsalinux/soulseek/
6. Template URL = https://hub.docker.com/r/danielguerra/soulseek/~/dockerfil
7. Icon URL = http://www.slsknet.org/news/sites/default/files/slsk_bird.jpg
8. WebUI = http://[IP]:[PORT:5950]/
9. Network Type = bridge
10. Privileged = Yes  (got fuse errors without this)
11. Click Add Another Path, Port or Variable : Select Host Path 
12. name = Appdata config path |  container path=/home/soulseek/.config/  | host path = /mnt/user/appdata/soulseek/config   
13. presume you have an "appdata" share, if not, create one, then mkdir -p this directory on unraid:  mkdir -p /mnt/user/appdata/soulseek/{config,Downloads,Music} 
14. on unraid : chown nobody.users -R /mnt/user/appdata/soulseek/* 
15. Click Add Another Path, Port or Variable : Select Host Path
16. name = Host Path 1 | Container Path = /home/soulseek/Music/  | host path = /mnt/user/appdata/soulseek/Music/
17. Click Add Another Path, Port or Variable : Select Host Path
18. name = Host Path 2 | Container Path = /home/soulseek/Downloads/  | host path = /mnt/user/appdata/soulseek/Downloads/
19. Click Add Another Path, Port or Variable : Select Host Path
20. name = Host Path 3 | Container Path = /home/soulseek/.SoulseekQt/  | host path = /mnt/user/appdata/soulseek/SoulseekQt/
21. Click Add Another Path, Port or Variable : Select Host Port
22. name = Host Port 1 | container port = 5900 | host port = 5950

From there, let it build, then open a vnc client and hit <unraid ip>:5950

1. Once you enter your user/pass, choose "/home/soulseek/Music" as your shared directory. 
2. Under File Sharing, click "Set Download Folder" and choose /home/soulseek/Music
3. Your config files should persist in /mnt/user/appdata/soulseek/config and load up when you rebuild the container. 
4. LIkewise, Downloaded Music should persist in /mnt/user/appdata/soulseek/Downloads. 
5. Add music you wish to share to /mnt/user/appdata/soulseek/Music , or just create a softlink to where you keep it on the array

 

Idk how this would get added to 'community apps', but if someone wants to let me know how that's done..

[realies]

Just pushed the latest version of Soulseek (2018.01) that works through a browser here.

[ridge]

Hey @realiesI just got this docker working, and I was wondering if you had a functioning reverse proxy going for it? I can't seem to get nginx to work on this novnc container. Thanks!

[realies]

@ridge, feel free to modify this, ssl.conf and proxy.conf are part of linuxserver.io's letsencrypt nginx server, but it should run fine without them, the key thing is the /websockify connection upgrade.

 

upstream soulseek {
        server 192.168.1.100:6080;
}

server {
        server_name _;
        listen 80;
        return 301 https://$host$request_uri;
}

server {
    server_name _;
    listen 443 ssl;

    access_log /config/log/nginx/soulseek_access.log;
    error_log /config/log/nginx/soulseek_error.log;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    location / {
        include /config/nginx/proxy.conf;
        proxy_pass http://soulseek/;
    }

    location /websockify {
        include /config/nginx/proxy.conf;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
        proxy_pass http://soulseek/;
    }
}

 

 

[ridge]

Perfect! I couldn't get it to work using a subdirectory. Switched to using a subdomain as in your example and we're golden. Thanks!

[realies]

Perhaps if you change `location /` to `location /subdir/` and leave the websockets to be at `location /websockify` it might work.

[ridge]

Hey @realies, wanted to ask if you'd seen any other instances of filenames not being parsed properly?

 

Eg, filename-error.png, attached. The correct filenames are in filename-proper.png, highlighted. As you can see, the docker is having trouble with special characters like umlauts, and curly single quotes.

 

My music is all tagged from Musicbrainz, and I know it's correct. I'd hate to have to go in and edit the filenames, and right now albums aren't sharing correctly. Any ideas?

[realies]

@ridge, I can't replicate. Sharing a Tiësto song indexes it, although it shows up as Ti?sto in the browse list. How do you get the errors from the first screenshot?

[ridge]

@realiesThey're like that in the upload window when someone tries to upload from me. I don't know what else to tell you.

[realies]

You mean to upload to you?

[ridge]

No, from me to them. So the screenshot I shared with the weird filenames is from the Uploads tab within Transfers. Here's another example

[realies]

@ridge, please update to the latest version of the image.

[ridge]

Looks like that worked. No errors from the last 24 hours or so. Thanks!

[realies]

You can now also change the resolution of the container with the environment variable `-e resolution=1280x720`.

[MrPotter]

@realiesevery time my container restarts Soulseek's configuration resets even though my configuration directory is on persistent storage. Any thoughts or has anyone else reported a similar issue?

[realies]

@MrPotter, https://github.com/realies/soulseek-docker/issues/1

[MrPotter]

On 9/24/2018 at 7:33 PM, realies said:

@MrPotter, https://github.com/realies/soulseek-docker/issues/1

Genius. I dropped the save every "x" minute from the default 60 to 20, and it appears to be working. Odd that the container had been running for days without a restart so the 60 should have been working. Maybe the value needs manipulated to start working? Thank you for the quick fix!

[xthursdayx]

On 4/22/2018 at 8:59 PM, realies said:

Just pushed the latest version of Soulseek (2018.01) that works through a browser here.

Hey @realies thanks for the container. Where does "/persistent/appdata" map to? Can I just change that to my preferred appdata location (e.g. /mnt/cache/appdata/soulseek"?

[realies]

@zandrsn, maybe you should read more about the high-level abstract of how Docker and Docker volumes work or at least try it the brute-force way before asking questions of this type.

[xthursdayx]

8 minutes ago, realies said:

@zandrsn, maybe you should read more about the high-level abstract of how Docker and Docker volumes work or at least try it the brute-force way before asking questions of this type.

Super helpful, thanks.