Self-host slskd with Levelrail
A modern web client and server for the Soulseek peer to peer network, with a REST API.
- Authorslskd
- LicenceAGPL-3.0-only
- Memory256 MiB
- Services1
Needs setup: set SLSKD_SLSK_PASSWORD, SLSKD_SLSK_USERNAME before the first start.
How to self-host slskd
-
Pull the images
One image is pulled on your server.
Show images
slskd/slskd:0.26.2
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 5030.
-
Fill in the secrets
1 secret is generated and stored encrypted, 2 settings are preset, you provide 2 values.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
After the first start
- Sign in as admin with the generated web password.
slskd requirements
- Memory
- About 256 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 5030
- Domain
- Optional, an sslip.io address is used without one
- Settings
- 2 to fill in
- License
- AGPL-3.0-only, network copyleft (agpl) license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then slskd. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the slskd docs page.
Deploy slskd your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy slskd from the CLI
levelrail-cli templates install slskd --name my-slskd --env SLSK_USERNAME=VALUE --env SLSK_PASSWORD=VALUE Deploy slskd with the API
curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
https://levelrail.example.com/api/v1/service-templates/slskd/install \
-d '{
"name": "my-slskd",
"env": { "SLSK_USERNAME": "VALUE", "SLSK_PASSWORD": "VALUE" }
}' slskd configuration
slskd services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| slskd | slskd/slskd:0.26.2 | 5030 | app -> /app |
slskd environment variables
| Variable | Service | Value |
|---|---|---|
| SLSKD_PASSWORD | slskd | Generated at deploy |
| SLSKD_REMOTE_CONFIGURATION | slskd | Preset by the template |
| SLSKD_SLSK_PASSWORD | slskd | You must set this |
| SLSKD_SLSK_USERNAME | slskd | You must set this |
| SLSKD_USERNAME | slskd | Preset by the template |
Ports and volumes
- Ports
- 5030
- Volumes
- 1 named mount: app -> /app
slskd FAQ
How much memory does slskd need?
The catalog lists about 256 MiB of memory for slskd.
Does slskd run on arm64?
For slskd, arm64 support is not confirmed; amd64 is unknown.
What licence is slskd under?
slskd is licensed under AGPL-3.0-only, which is network copyleft, so source sharing also applies when it is offered as a hosted service.
Does slskd need configuration before it starts?
Yes. slskd has required settings: SLSKD_SLSK_PASSWORD and SLSKD_SLSK_USERNAME.
Which ports does slskd use?
slskd listens on port 5030 inside the stack.
Where does slskd keep its data?
In a named volume: app mounted at /app.
Can I deploy slskd on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for slskd, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image slskd/slskd:0.26.2 is what you deploy there.