# SeaweedFS SeaweedFS is a fast, highly scalable distributed file system and S3-compatible object store for storing and serving very large numbers of files. It is open source and self-hosted, installable on Docker Hub, Kubernetes (Helm), Proxmox, TrueNAS and Unraid. Canonical page: https://ourlocalhost.com/app/445/seaweedfs ## Description SeaweedFS is a fast, highly scalable distributed file system and S3-compatible object store for storing and serving very large numbers of files. This plug-and-play Unraid Community Applications template runs the official chrislusf/seaweedfs image in single-node "mini" mode: master, volume server, filer, S3 API and admin UI all in one container, with all data under one persistent /data mount. This is SeaweedFS's own documented single-node setup, not a cut-down mode - the same binary scales out to a real cluster later by adding volume servers elsewhere if you ever need that. It is a genuinely maintained, actively developed alternative now that MinIO's open-source Community Edition has been archived (Apr 2026) and its Docker images stopped receiving security updates in Sep 2025. ## Platform availability Available on 4 of 9 platforms: Unraid, TrueNAS, Proxmox, Helm. ## Health score 85/100 (Excellent), based on 4 of 4 factors. - Maintained: 100 (last commit 17 days ago) - Popular: 91 (35,290 GitHub stars) - Easy to install: 65 (4 install platforms, install notes, Docker image) - Light to run: 60 (2 GB minimum RAM, runs on ARM) ## Links - Official website: https://seaweedfs.com - GitHub: https://github.com/seaweedfs/seaweedfs - Docker Hub: https://hub.docker.com/r/chrislusf/seaweedfs - Documentation: https://seaweedfs.com/docs/eula/ - Kubernetes (Helm): https://artifacthub.io/packages/helm/seaweedfs/seaweedfs - Proxmox: https://community-scripts.github.io/ProxmoxVE/scripts?id=seaweedfs - TrueNAS: https://apps.truenas.com/catalog/seaweedfs/ - Unraid: https://ca.unraid.net/apps/seaweedfs-0f9mbrl17bnwv1?q=SeaweedFS ## Common questions ### Should SeaweedFS metadata and volume directories be placed in /tmp? No. Point the master metadata -mdir and volume data -dir at stable, backed-up folders rather than temporary /tmp paths. If /tmp is used, the system may clear it later and you could lose files or metadata. ### Why might volume or filer servers fail to connect or save files? Start the master before the volume and filer servers and set each component's normal port and gRPC port consistently. If the master is not running or the ports are blocked, the servers may fail to connect or save files. ### What FUSE problem have users seen when copying directories? Users report read errors on directories mounted with SeaweedFS FUSE. Copy operations on those mounts may hang and cannot be stopped. ### Do I need to install the weed command before starting SeaweedFS server commands? Yes. Run the install script first so the weed command is placed in /usr/local/bin. Without it, the server commands won't exist. ### How can I grow SeaweedFS capacity after a single-node setup? Capacity grows by starting another volume server. The same weed binary can serve the S3 object store, POSIX file system, and lakehouse over the same data. ## Alternatives - GlusterFS: GlusterFS is a scale-out network-attached storage file system. - MinIO: MinIO is a self-hosted, high-performance, Amazon S3-compatible object storage service that stores and manages data for backups, machine lea… --- Source: Our Local Host (https://ourlocalhost.com/app/445/seaweedfs), the self-hosted and open-source app directory.