The s3s project provides Docker images for the following binaries:
s3s-fs: File system-based S3 implementations3s-e2e: End-to-end testing binarys3s-proxy: Proxy implementation
Docker images are published to GitHub Container Registry (GHCR) at:
ghcr.io/s3s-project/s3s
- Version tags:
0.16.1,0.16(for released versions, generated from git tags likev0.16.1) 0: the highest released0.xversion (it mirrorslatestwhile the project is at major version zero)latest: latest stable release; it only moves forward. Pre-releases and patch releases from an older maintenance line (when a newer release already exists) do not update itedge: build of themainbranch; refreshed by every release tagged onmainand rebuilt weekly
Images are built for the following platforms:
linux/amd64(x86_64)linux/arm64(ARM64/aarch64)
# Pull the latest stable version
docker pull ghcr.io/s3s-project/s3s:latest
# Pull a specific version
docker pull ghcr.io/s3s-project/s3s:0.12.0
# Pull the edge build
docker pull ghcr.io/s3s-project/s3s:edgeThe default command shows help for s3s-fs:
docker run --rm ghcr.io/s3s-project/s3s:latestTo run s3s-fs server:
docker run --rm -p 8014:8014 ghcr.io/s3s-project/s3s:latest ./s3s-fs --host 0.0.0.0 --port 8014To run other binaries:
# s3s-proxy
docker run --rm ghcr.io/s3s-project/s3s:latest ./s3s-proxy --help
# s3s-e2e
docker run --rm ghcr.io/s3s-project/s3s:latest ./s3s-e2e --help- Base image:
scratch(minimal, static binaries) - Binaries: Statically compiled with musl for minimal size
- Size: Optimized for small footprint
- Security: No shell or unnecessary tools included
To build the Docker image locally:
docker build -f docker/Dockerfile -t s3s:local .Note: Docker images were previously published to Docker Hub. As of the migration, all new releases are published to GitHub Container Registry (ghcr.io). Please update your scripts and configurations to use the new registry location.
Old location (deprecated):
<username>/s3s
New location:
ghcr.io/s3s-project/s3s