A plug-and-play Unraid Community Applications template for SeaweedFS - a fast, S3-API-compatible object store, actively maintained (weekly releases), wrapping the official chrislusf/seaweedfs image.

Maintained solo, in whatever spare time there is. Questions via the support thread, bugs, ideas and feature requests via GitHub issues. If it's useful to you, a coffee is always welcome.

Table of Contents

1. Why this instead of MinIO?
2. What is this?
3. Quick Start on Unraid
4. Connecting a client
5. Coming from MinIO
6. Configuration
7. Backup
8. How AI is used here
9. Support this project

1. Why this instead of MinIO?

MinIO's open-source Community Edition is done: the minio/minio repo was archived in April 2026, its last Docker Hub image (September 2025) has a known unpatched high-severity CVE, and the last source release ever cut (October 2025, source-only, never packaged as an image) was the final one. MinIO now pushes AIStor instead - a free tier exists, but it is closed-source, not a continuation of the open MinIO you used to run.

SeaweedFS is a genuine, actively-developed alternative: Apache-2.0, near-weekly releases, an official multi-arch image actually being maintained, and a documented single-node S3 mode that isn't a cut-down fallback - it's the same binary a real cluster uses, just running every role in one process.

2. What is this?

SeaweedFS's own "mini" mode runs master, volume server, filer, S3 API and admin UI together in a single process, all data under one directory. This template wraps the official image running exactly that mode, with the data directory mapped to Unraid appdata so it survives recreation and updates - nothing more added, nothing hidden.

File ownership inside the data volume is fixed automatically by the image's own entrypoint (a built-in seaweed user, chowned on start) - there's no PUID/PGID to configure.

3. Quick Start on Unraid

1. Install from Community Applications, or add this template's URL directly: https://raw.githubusercontent.com/junkerderprovinz/unraid-apps/main/seaweedfs/seaweedfs.xml
2. Set Access Key and Secret Key (see Security note below) - anything reasonably random works, e.g. generate a secret with openssl rand -hex 24.
3. Optionally set Pre-create Bucket to a name (or comma-separated names) you want to exist immediately.
4. Start the container. The S3 endpoint is http://SERVER_IP:8333; the admin UI (bucket/volume/topology browser) is at http://SERVER_IP:23646.

Security: leaving both keys empty starts the S3 API in unauthenticated "Allow All" mode. That's fine for a five-minute local test, not for anything you actually care about - set both before storing real data, and don't expose port 8333 to the internet without a reverse proxy and TLS in front of it.

4. Connecting a client

Any S3-compatible tool works. A few common ones:

rclone (rclone config, or a config file entry):

[seaweedfs]
type = s3
provider = Other
access_key_id = YOUR_ACCESS_KEY
secret_access_key = YOUR_SECRET_KEY
endpoint = http://SERVER_IP:8333

MinIO Client (mc) - yes, the CLI tool still works fine against SeaweedFS:

mc alias set seaweedfs http://SERVER_IP:8333 YOUR_ACCESS_KEY YOUR_SECRET_KEY
mc mb seaweedfs/my-bucket
mc cp somefile.txt seaweedfs/my-bucket/

restic (repository URL):

export AWS_ACCESS_KEY_ID=YOUR_ACCESS_KEY
export AWS_SECRET_ACCESS_KEY=YOUR_SECRET_KEY
restic -r s3:http://SERVER_IP:8333/my-restic-repo init

5. Coming from MinIO

There is no automatic import - copy your data across with any S3-to-S3 tool. rclone is the simplest:

rclone config   # add both the old MinIO and this SeaweedFS instance as remotes
rclone sync minio-remote:my-bucket seaweedfs-remote:my-bucket --progress

mc mirror works the same way if you'd rather stay in the MinIO Client tool (it talks to any S3-compatible endpoint, including SeaweedFS, on both sides).

Point whatever was using the old endpoint (backup tools, apps, scripts) at the new http://SERVER_IP:8333 and the new Access/Secret Key once the copy is verified.

6. Configuration

7. Backup

Everything lives under the single Data mount (/mnt/user/appdata/seaweedfs/data by default) - back that up the same way you back up any other appdata folder (e.g. with a container-aware backup tool). There's no separate database or config store to remember.

8. How AI is used here

One knight builds this, and AI is one of the tools I work with, the same way I work with an editor or a compiler. It helps me write code and documentation and it checks my work, and that saves me a good many evenings. It does not make the decisions, though. I read and understand everything before it ships, and if something here breaks, that is on me and not on the tool.

You do not have to take my word for it. The code is open and every release note is written by hand. The issue tracker shows how problems actually get handled, including the ones I got wrong the first time. If you find something that is not right, open an issue and I will look at it.

9. Support this project

Questions? Check the support thread. Bugs, ideas or feature requests? Please open a GitHub issue.

This is a one-person project. I put a lot of time and effort into building and maintaining it, in whatever free time I have. If it's helped you, I'd genuinely appreciate the support: you're welcome to buy me a coffee.