Self-host Linkding with Levelrail

Verified

A minimal, fast bookmark manager built for keeping a personal link archive.

  • AuthorsissbrueckerVerified by Levelrail
  • LicenceMIT
  • Memory128 MiB
  • Archarm64
  • Services1

How to self-host Linkding

  1. Pull the images

    One image is pulled on your server.

    Show images
    • sissbruecker/linkding:1.31.0
  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 requirements

Memory
About 128 MiB
Architectures
amd64 image published, arm64 tested
Ports
9090
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
MIT, permissive license
  • Verified. Verified on arm64 with image tag 1.31.0. Our CI ran this exact image version and it answered on its health path. Evidence
  • 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. 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 docs page.

Deploy Linkding your way

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

Deploy Linkding from the CLI

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

Deploy Linkding 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/deploy

Linkding configuration

Linkding services

ServiceImagePortsVolumes
linkding sissbruecker/linkding:1.31.0 9090 linkding_data -> /etc/linkding/data

Linkding environment variables

VariableServiceValue
LD_SUPERUSER_NAME linkding Generated at deploy
LD_SUPERUSER_PASSWORD linkding Generated at deploy

Ports and volumes

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

Linkding FAQ

How much memory does Linkding need?

The catalog lists about 128 MiB of memory for Linkding.

Does Linkding run on arm64?

For Linkding, arm64 is tested; amd64 is image published.

What licence is Linkding under?

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

Does Linkding need configuration before it starts?

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

Which ports does Linkding use?

Linkding listens on port 9090 inside the stack.

Where does Linkding keep its data?

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

Can I deploy Linkding 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 linkding for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image sissbruecker/linkding:1.31.0 is what you deploy there.

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