Self-host PairDrop with Levelrail
VerifiedAn AirDrop-style app for sending files and messages between devices on the same network, from any browser.
- Authorschlagmichdoch
- LicenceGPL-3.0
- Memory256 MiB
- Archarm64
- Services1
How to self-host PairDrop
-
Pull the images
One image is pulled on your server.
Show images
lscr.io/linuxserver/pairdrop:1.11.2
-
Create the app
One service starts in a single Compose app, on port 3000.
-
Fill in the secrets
4 settings are preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
PairDrop requirements
- Memory
- About 256 MiB
- Architectures
- amd64 image published, arm64 tested
- Ports
- 3000
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- GPL-3.0, copyleft license
- Verified. Verified on arm64 with image tag 1.11.2. Our CI ran this exact image version and it answered on its health path. Evidence
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then PairDrop. 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 PairDrop docs page.
Deploy PairDrop your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy PairDrop from the CLI
levelrail-cli templates install pairdrop --name my-pairdrop Deploy PairDrop with the API
curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
https://levelrail.example.com/api/v1/service-templates/pairdrop/install \
-d '{
"name": "my-pairdrop"
}' PairDrop configuration
PairDrop services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| pairdrop | lscr.io/linuxserver/pairdrop:1.11.2 | 3000 | none |
PairDrop environment variables
| Variable | Service | Value |
|---|---|---|
| PGID | pairdrop | Preset by the template |
| PUID | pairdrop | Preset by the template |
| RATE_LIMIT | pairdrop | Preset by the template |
| TZ | pairdrop | Preset by the template |
Ports and volumes
- Ports
- 3000
- Volumes
- none
PairDrop FAQ
How much memory does PairDrop need?
The catalog lists about 256 MiB of memory for PairDrop.
Does PairDrop run on arm64?
For PairDrop, arm64 is tested; amd64 is image published.
What licence is PairDrop under?
PairDrop is licensed under GPL-3.0, which is copyleft, so changes you distribute must be shared under the same terms.
Does PairDrop need configuration before it starts?
No. The template fills in its own defaults.
Which ports does PairDrop use?
PairDrop listens on port 3000 inside the stack.
Can I deploy PairDrop on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id pairdrop for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image lscr.io/linuxserver/pairdrop:1.11.2 is what you deploy there.