← Directory

SeaweedFS

SeaweedFS is a fast, S3-API-compatible object store - a genuinely maintained, actively developed alternative now that MinIO's open-source Community Edition…

  • Backup
  • Cloud
  • Network Services
  • Tools & Utilities
SeaweedFS is a fast, S3-API-compatible object store - 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. This is a plug-and-play Unraid Community Applications template wrapping the OFFICIAL chrislusf/seaweedfs image. Runs the "mini" single-process mode by default: master, volume, filer, S3 API and admin UI all in one container, 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. S3 CLIENTS (rclone, mc, aws-cli, restic, most S3 SDKs) point at http://SERVER_IP:8333 with the access key / secret key set below - no other setup needed, a bucket is pre-created if you set

Platform availability

Available on 4 of 9 platforms

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.

85/100 Excellent

Maintained
100last commit 8 days ago
Popular
9135,290 GitHub stars
Easy to install
654 install platforms, install notes, Docker image
Light to run
602 GB minimum RAM, runs on ARM

Availability: platform listings confirmed today, links checked 16 days ago

GitHub stars
35,290
Open issues
791
Last commit
2026-10-07
Latest release
4.48
License
Apache-2.0
Activity
rising

Checked 8 days ago - source: GitHub (seaweedfs/seaweedfs)

Resources & Compatibility

Minimum requirements: 2 GB RAM, 2 CPU core(s), 100 GB disk. ARM (e.g. Raspberry Pi) is supported.

Checked 17 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Install the SeaweedFS command first Run the install script from the main README before starting anything. It puts the weed command in /usr/local/bin, a standard Linux command folder, and without it the server commands won't exist. source
  • Start master first and set ports Start the master before the volume and filer servers, and make sure each component's normal port and its gRPC (internal messaging) port are set consistently. If the master is not running or those ports are blocked, the servers may fail to connect or save files. source
  • Use stable folders for data and metadata Point master metadata (-mdir) and volume data (-dir) at stable, backed-up folders rather than temporary /tmp paths. If you use /tmp, the system may clear it later and you could lose your files or their metadata. source

Fetched 17 days ago - each note links to its source

Alternatives (2)

  • 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…

Checked 14 days ago - source: AlternativeTo

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.

Answers sourced from github.com, github.com, github.com, github.com, www.reddit.com

Community

Collected 16 days ago - public community threads