readystack/seaweedfs repository overview

⁠SeaweedFS

readystack/seaweedfs:4.51-CE-ubuntu24.04-r1

Source, recipe and records

• Source and build recipe: https://readystack.dev/products/seaweedfs/recipe⁠
• Upstream source at this release's pinned commit (4.51): https://github.com/seaweedfs/seaweedfs/tree/153ab668c99731a6d29492bf6c61d0b4fa701101⁠
• Product page: https://readystack.dev/products/seaweedfs⁠
• Hermetic Build Kit for this release (free with an account): https://readystack.dev/products/seaweedfs⁠
• Release history (JSON): https://readystack.dev/api/releases/seaweedfs⁠
• Defect record: https://readystack.dev/defects.html?product=seaweedfs⁠
• Today's scan: https://readystack.dev/products/seaweedfs#pp-grade⁠
• Report an issue: https://github.com/ReadyStackFree/readystack/issues/new?template=bug.yml&product=seaweedfs⁠
• Signing key (cosign): https://readystack.dev/keys/cosign.pub⁠

A cosign-signed build of github.com/seaweedfs/seaweedfs 4.51 (Apache-2.0 — distributed S3-compatible object storage), built clean-room from official upstream source by ReadyStack⁠.

⁠Who uses it and why

Who: Teams who need to store very large numbers of files, for applications, backups or analytics, on their own servers.

Why: SeaweedFS is a simple, highly scalable distributed storage system. One server program offers an object store, a POSIX file system and table storage over the same data, and capacity grows by adding volume servers.

Use case: A photo-sharing service stores huge numbers of small images that a single file server can no longer handle. SeaweedFS packs them into volumes spread across servers, reads each one with a single disk read, and grows by starting another volume server when space runs low.

About the upstream project, written from its own description: https://github.com/seaweedfs/seaweedfs⁠

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:0eb77b3aac7b88d7714071ebd863825ac9536e44933d59b3a90ed452d67f7701 on 2026-10-29.

• Scan scores — we scan every image we publish every day (an SBOM made with syft, vulnerabilities matched with grype, scored with cerodeo-v1, the rubric ce.rodeo published until 2026-10-26) and record each scan with how its score was derived. This release's first and latest scan: https://readystack.dev/products/seaweedfs⁠
• ReadyStack release check — passed at release on 2026-10-28: no fixable critical or high vulnerability (Docker Scout and OSV), a non-root user, SBOM and provenance attached. This is ReadyStack's own test, not a Docker grade; vulnerabilities published since then are in today's result at https://readystack.dev/queue⁠.
• Signed — cosign signature by the ReadyStack release key (fingerprint 04daa92344a52dbc) on this release's index digest sha256:0eb77b3aac7b88d7714071ebd863825ac9536e44933d59b3a90ed452d67f7701; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/seaweedfs:4.51-CE-ubuntu24.04-r1.
• Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
• Runs as a non-root user (seaweedfs).
• Built from source by ReadyStack.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is 4.51-CE-ubuntu24.04-r1 — the release listed at readystack.dev. Release tags use the pattern <upstream-version>-CE-<base-os>-r<N>; the current one is signed, attested (SBOM + provenance), and is provided under the ReadyStack Agreement⁠.

• Earlier release tags (an older version or revision in the same pattern) are superseded. They stay pullable so existing deployments can pin them, but they are no longer re-graded, and fixes appear only in newer releases: move to the current release. For a superseded release's build kit, ask support.

• Release tags never move, so pulling the same tag again never changes the image. To be offered each new release automatically (a new revision r<N+1>, or a new upstream version), use the ReadyStack Renovate preset: https://readystack.dev/updates.html⁠

• Any tag beginning with internal- is an engineering-pipeline artifact published for build observability. It is unsupported, may change or disappear without notice, and must not be used in production.

# ✓ current release
docker pull readystack/seaweedfs:4.51-CE-ubuntu24.04-r1

# ✗ unsupported (do not pull)
docker pull readystack/seaweedfs:internal-...

This release is signed; verify it with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/seaweedfs:4.51-CE-ubuntu24.04-r1 (the signature is recorded in the public Sigstore transparency log). Support: [email protected]⁠, as set out in the ReadyStack Agreement⁠.

⁠Deployment

Single container, single static Go binary (weed, CGO-free), foreground weed server -s3. Master+volume+filer+S3 in one process: the S3 API on :8333 is the one port meant for clients; the filer, master and volume server listen on the container's loopback interface only (see Ports in the handbooks). Object storage — data + metadata under /data. NO SQL DB, NO sidecar (production scales master/volume/filer as separate roles; this image is the single-node S3 endpoint).

Secrets go in an env file that only you can read, not on the command line, and passwords that only set up the first start come out of it after setup. Create seaweedfs.env with install -m 600 /dev/null seaweedfs.env, then write these lines into it with an editor, with your own values (a value typed into a shell stays in its history). Docker reads each line as written: no quotes around a value, no spaces around =.

# The S3 admin identity's access key and secret key; both are needed at every start.
SEAWEEDFS_S3_ACCESS_KEY=YOUR_ACCESS_KEY
SEAWEEDFS_S3_SECRET_KEY=YOUR_SECRET_KEY

docker run -d --name seaweedfs -p 8333:8333 --env-file ./seaweedfs.env -v seaweedfs-data:/data readystack/seaweedfs:4.51-CE-ubuntu24.04-r1

Starts a single SeaweedFS server (master+volume+filer+S3 in one process) with its data in the seaweedfs-data volume. SEAWEEDFS_S3_ACCESS_KEY and SEAWEEDFS_S3_SECRET_KEY in seaweedfs.env are required at every start (or a mounted SEAWEEDFS_S3_CONFIG identities file): without them the container exits at once (see Required and optional environment in the handbooks). /healthz answered 200 within about 3-11 seconds on a fresh boot (tested; on existing data see Health check in the handbooks) and does not need credentials, even once they are configured. Only port 8333 (S3) is published by the run command above, on all interfaces: credentials are required by default (see Access control and passwords in the handbooks), and an unsigned request gets 403 AccessDenied (tested). Do not publish any other port: 18333 (the S3 gateway's gRPC port) refuses every call without the container's admin token and no client outside the container needs it; 8888 (filer), 9333 (master) and 8080 (volume) listen on the container's loopback interface only, so a published mapping to them only resets connections (tested) — see Ports in the handbooks. The Iceberg REST Catalog (:8181) and Lance Namespace server (:9101) are disabled (tested: no listener). Extra arguments after readystack/seaweedfs:4.51-CE-ubuntu24.04-r1 replace the default CMD (server -s3 -ip=127.0.0.1 -ip.bind=127.0.0.1 -s3.ip.bind=0.0.0.0 -s3.port.iceberg=0 -s3.port.lance=0 -filer.disableHttp) entirely, so repeat those flags when you add your own; the entrypoint still puts -volume.max=0 before them (a later -volume.max wins) and appends -dir=/data and -master.volumeSizeLimitMB=1024 after them, which cannot be overridden this way (tested). The archive ships no Compose file.

⁠The full ReadyStack Hermetic Build Kit

The complete --network=none build kit for this image — plus admin/DB/API handbooks, the build's validation records, and its build provenance records — is a free download for any registered account at readystack.dev/products/seaweedfs⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:fb4d5307636bf34f2142e9308fd643c4da38ef2ca601b41fff21cf55f02c6a5a on 2026-10-28.

— ReadyStack · readystack.dev