Self-host Linkding Plus with Levelrail

Linkding's extended image with full-page snapshot archiving bundled in, for bookmarks that must survive link rot.

  • Authorsissbruecker
  • LicenceMIT
  • Memory256 MiB
  • Archarm64
  • Services1

How to self-host Linkding Plus

  1. Pull the images

    One image is pulled on your server.

    Show images
    • sissbruecker/linkding:1.47.0-plus
  2. Create the app

    One service starts in a single Compose app, with 1 named volume mount for your data, on port 9090.

  3. Fill in the secrets

    2 secrets are generated and stored encrypted, you do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

Linkding Plus requirements

Memory
About 256 MiB
Architectures
amd64 image published, arm64 image published
Ports
9090
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
MIT, permissive license
  • Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
  • Host ports. It publishes port 9090 on the host, so open them in the VPS firewall only if you want that.

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Linkding Plus. 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 Linkding Plus docs page.

Deploy Linkding Plus your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy Linkding Plus from the CLI

levelrail-cli templates deploy linkding-plus --name my-linkding-plus

Deploy Linkding Plus with the API

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/linkding-plus/deploy

Linkding Plus configuration

Linkding Plus services

ServiceImagePortsVolumes
linkding-plus sissbruecker/linkding:1.47.0-plus 9090 linkding_plus_data -> /etc/linkding/data

Linkding Plus environment variables

VariableServiceValue
LD_SUPERUSER_NAME linkding-plus Generated at deploy
LD_SUPERUSER_PASSWORD linkding-plus Generated at deploy

Ports and volumes

Ports
9090
Volumes
1 named mount: linkding_plus_data -> /etc/linkding/data

Linkding Plus FAQ

How much memory does Linkding Plus need?

The catalog lists about 256 MiB of memory for Linkding Plus.

Does Linkding Plus run on arm64?

For Linkding Plus, an arm64 image is published; amd64 is image published.

What licence is Linkding Plus under?

Linkding Plus is licensed under MIT, which is permissive, with few conditions on reuse.

Does Linkding Plus need configuration before it starts?

No. The template fills in its own defaults and generates secrets at deploy time.

Which ports does Linkding Plus use?

Linkding Plus listens on port 9090 inside the stack.

Where does Linkding Plus keep its data?

In a named volume: linkding_plus_data mounted at /etc/linkding/data.

Can I deploy Linkding Plus 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 Linkding Plus, 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 sissbruecker/linkding:1.47.0-plus is what you deploy there.

levelrail-cli templates deploy linkding-plus --name my-linkding-plus