Longhorn
Longhorn is a lightweight, reliable, and powerful distributed block storage system built on and for Kubernetes.
Platform availability
Available on 1 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
78/100 Good
- Maintained
- 100last commit 12 days ago
- Popular
- 788,053 GitHub stars
- Easy to install
- 251 install platform, install notes
- Light to run
- No data
- Security check
- 85no serious findings, CI, tests, OpenSSF Scorecard 6.2/10
Based on 4 of 5 factors.
Availability: platform listings confirmed today
- GitHub stars
- 8,053
- Open issues
- 1936
- Last commit
- 2026-11-09
- Latest release
- v1.13.0
- License
- Apache-2.0
- Activity
- declining
Checked 12 days ago - source: GitHub (longhorn/longhorn)
Resources & Compatibility
Requirements not published yet.
First-install notes
- Confirm a test volume attaches After install, create a small test volume and attach it, then run kubectl -n longhorn-system get volume; kubectl is the command-line tool for your Kubernetes cluster, and -n longhorn-system selects Longhorn's namespace (its project area). You should see it attached; if not, Longhorn isn't ready and your apps will fail to mount storage. source
- Plan erasure coding capacity If you enable erasure coding (a method that stores data and extra repair information across multiple disks instead of making full copies), usable space is lower than the raw disk total. The example with 2 data disks and 2 parity (repair) disks gives 50% usable capacity, so size your storage accordingly. source
Fetched 46 days ago - each note links to its source
Variants
Alternatives (1)
- Maya API Server - Maya API Server is the OpenEBS control-plane component that orchestrates cloud-native, application-aware storage engines such as Jiva and cā¦
Checked 52 days ago - source: AlternativeTo
Common questions
Which disk image formats can Longhorn backing images use?
Longhorn backing images can be qcow2 or raw disk image files.
Can Longhorn storage be shared to a NAS over NFS?
A community thread discusses sharing Longhorn storage to a NAS over NFS.
What can cause Longhorn performance issues?
Latency can build up per IOP, and underlying RAID 5/6 or a non-write-caching hardware RAID controller can add extra latency.
Which logs are most useful for troubleshooting Longhorn?
Check the Longhorn Manager and Engine logs, especially the longhorn-manager and instance-manager pods.
Can Longhorn back a Plex volume in a k3s cluster?
A user describes using Longhorn storage for Plex running in Docker on Kubernetes in a k3s cluster with Raspberry Pi 5 NVMe nodes.
Answers sourced from github.com, longhorn.io, www.reddit.com, www.reddit.com, www.reddit.com
Community
- Setup plex in docker on top of kubernetes using portainer and ... - Reddit (reddit)
- Longhorn to nas NFS : r/selfhosted - Reddit (reddit)
- r/selfhosted on Reddit: Fix Longhorn Volumes Stuck in Attach/Detach ... (reddit)
- k8s and storage : r/selfhosted - Reddit (reddit)
- How can I better consolidate this architecture? : r/selfhosted - Reddit (reddit)
- r/selfhosted on Reddit: Overwhelmed by persistent storage on Kubernetes ... (reddit)
Collected 48 days ago - public community threads