![Linkding]()
Linkding
Container
Self-hosted bookmark manager that is minimal and fast. Source: https://github.com/sissbruecker/linkding
Image details
Source details
Configuration
TypeContainerlinuxsissbruecker/linkding:latest9090:9090/tcp/etc/linkding/dataLD_SUPERUSER_NAME=adminLD_SUPERUSER_PASSWORD=changemeLD_SUPERUSER_EMAIL=unless-stoppedStandalone Install
Select an install method, to see config/commands for deploying Linkding
Install on Portainer
Import all app templates into your Portainer instance, for easy 1-click deploys
- Ensure both Docker and Portainer are installed, and up-to-date
- Log into your Portainer web UI
- Under Settings → App Templates, paste the below URL
- Head to Home → App Templates, and the list of apps will show up
- Select Linkding, fill in any config options, and hit Deploy
Template Import URL
https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me
More install options in our documentation, or see sissbruecker/linkding for app-specific guidance.
Introduction
linkding is a bookmark manager that you can host yourself. It's designed be to be minimal, fast, and easy to set up using Docker.The name comes from:
- link which is often used as a synonym for URLs and bookmarks in common language
- Ding which is German for thing
- ...so basically something for managing your links
Feature Overview:
- Clean UI optimized for readability
- Organize bookmarks with tags
- Bulk editing, Markdown notes, read it later functionality
- Share bookmarks with other users or guests
- Automatically provides titles, descriptions and icons of bookmarked websites
- Automatically archive websites, either as local HTML file or on Internet Archive
- Import and export bookmarks in Netscape HTML format
- Installable as a Progressive Web App (PWA)
- Extensions for Firefox and Chrome, as well as a bookmarklet
- SSO support via OIDC or authentication proxies
- REST API for developing 3rd party apps
- Admin panel for user self-service and raw data access
Demo: https://demo.linkding.link/
Screenshot:
Getting Started
The following links help you to get started with linkding:- Install linkding on your own server or check managed hosting options
- Install the browser extension
- Check out community projects, which include mobile apps, browser extensions, libraries and more
Serve Linkding on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.
Proxying linkding.example.com to http://linkding:9090
Add this to your Caddyfile
linkding.example.com {
reverse_proxy http://linkding:9090
}Check the logs first
Nine times out of ten the logs tell you exactly what went wrong.
- In Portainer, go to Containers, click the container, then Logs. Or run
docker logs linkding - Exit codes help too:
137means killed, usually out of memory.126or127means the command inside the image is broken.
Port already in use
If deployment fails with "Bind for 0.0.0.0:9090 failed: port is already allocated", something else on your server is using that port.
- Find what's using it:
sudo ss -tlnp | grep :9090 - Stop the other service, or pick a different host port. In
9090:9090only the left number is yours to change, the right one belongs to the app.
Running but the page won't load
The container is up but nothing appears in your browser.
- Use your server's real IP:
http://your-server-ip:9090. The 0.0.0.0 link Portainer shows isn't a real address. - Give it a minute after first deploy, linkding can take a while to initialise.
- Make sure your firewall allows the port, e.g.
sudo ufw allow 9090
Image won't pull
Test the pull directly on the host: docker pull sissbruecker/linkding:latest
- "manifest unknown" means the tag no longer exists. This template uses
latest, so try pinning a specific version instead. - "toomanyrequests" is the Docker Hub rate limit. Log in with
docker loginto raise it. - "no space left on device" means a full disk. Reclaim space with
docker system prune
"exec format error"
This means the image was built for a different CPU architecture than your server.
- This image supports:
amd64, arm64, arm/v7, arm64/v8 - Check yours with
uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.
Container keeps restarting
The unless-stopped restart policy relaunches the app after every crash, so the real error can scroll past.
- Check the logs right after a restart, the last few lines before it died are the useful ones.
- Get the exit code with
docker inspect linkding --format '{{.State.ExitCode}}' - Still stuck? Redeploy once with the restart policy set to
noso the failure stays visible.
Required settings are blank
LD_SUPERUSER_EMAIL has no default value, and linkding may crash or misbehave if left empty.
- Fill it in on the deploy screen before hitting deploy.
Raise an issue
Found something which isn't working as it should? Here's how to report it.
- Bug within the app: Open an issue on sissbruecker/linkding
- Template not working: Open an issue within the template's repo
- This website not working: Open an issue on lissy93/portainer-templates
A single container
Linkding runs as one container, the simplest kind of app here. Just the one image to pull and nothing else wired up alongside it.
The app image
An image is the app packed up ready to go, everything Linkding needs bundled into one download. This template pulls sissbruecker/linkding:latest, which Docker fetches once (about 383 MB) and then starts your own copy from.
Where the image comes from
Docker pulls its images from registries, public libraries of ready-built apps. Linkding's comes from Docker Hub, published by sissbruecker.
Version tags
The bit after the colon in the image name is the version tag. Here it's latest, which always points at the newest build, so a redeploy can bump you to a newer release without you asking. Newest right now is 1.46.1-plus-alpine. Pin a specific tag if you would rather stay on one version.
Which machines it runs on
Every image is built for particular CPU types. This one ships for amd64, arm64, arm/v7, arm64/v8, so it runs on both regular x86 servers and ARM boards like a Raspberry Pi.
Ports
A port is the door the app answers on. A mapping like 9090:9090 means it's reachable on port 9090 of your server, where the left number is yours to change and the right one belongs to the app. It opens:
9090:9090
Volumes
A volume is where Linkding keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:
/etc/linkding/dataas a volume Docker manages for you
Environment variables
Environment variables are the settings you hand over when you deploy, things like a password or a timezone. Linkding takes 3 of them, and one needs a value before it'll start properly:
LD_SUPERUSER_NAME, defaults toadmin. Admin usernameLD_SUPERUSER_PASSWORD, defaults tochangeme. Admin passwordLD_SUPERUSER_EMAIL, needs a value. Admin email (optional)
Restart policy
The restart policy here is unless-stopped, so Docker restarts Linkding after a crash or reboot, but leaves it off when you stop it on purpose. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).
Networking
Nothing custom is set, so Linkding sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.
Container name
Once it's deployed, Portainer names the container linkding. That's what you'll spot in the containers list and use in commands like docker logs linkding.
Platform
The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.
Open source license
Linkding is open source, released under the MIT license. In plain terms the code is out in the open, so you're free to run it and change it to fit what you need.
Portainer app templates
Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Linkding up. Add the template list to Portainer once, then deploying Linkding is a click rather than a wall of config.