scality/s3server repository overview

S3Server is being renamed Cloud Server and part of Scality Zenko, Scality⁠’s Open Source Multi-Cloud Data Controller. Learn more about Zenko at Zenko.io⁠

You can find Cloud Server image here⁠. If you have any questions please ask on Zenko Forum⁠.

⁠Supported tags and respective Dockerfile links

⁠Running S3 Server with a file backend

• 6018536a, latest (Dockerfile)⁠
• d75a5612 (Dockerfile)⁠
• 39cf1fae (Dockerfile)⁠
• bb2a38c0 (Dockerfile)⁠
• d75e2c9 (Dockerfile)⁠
• 246ada5 (Dockerfile)⁠
• 41bd9ad (Dockerfile)⁠

⁠Run S3 Server with an in-memory backend

• mem-6018536a, mem-latest (Dockerfile)⁠
• mem-d75a5612 (Dockerfile)⁠
• mem-39cf1fae (Dockerfile)⁠
• mem-bb2a38c0 (Dockerfile)⁠
• mem-d75e2c9 (Dockerfile)⁠
• mem-246ada5 (Dockerfile)⁠
• mem-41bd9ad (Dockerfile)⁠

⁠Quick reference

• Where to get help: Open an issue on Github⁠, Check our website⁠, or just our documentation⁠

• Where to file issues: Our Github repo⁠

• Maintained by: Open-source community⁠ and Scality permanent staff⁠

• Published image artifact details: Coming soon!

• Source of this description: Coming soon!

• Supported Docker versions: The latest release⁠, and we run from 1.10

⁠Quick start

The default access key is accessKey1, with the secret key verySecretKey1

⁠Run s3 server with a file backend on port 8000:

$ docker run -d --name s3server -p 8000:8000 scality/s3server

⁠Run s3 server with an in-memory backend on port 8000:

$ docker run -d --name s3server -p 8000:8000 scality/s3server:mem-latest

Note that the --name selected (in the example 's3server') will enable you to easily start and stop the given named container:

$ docker stop s3server
$ docker start s3server

⁠Continuous integration testing || in production usage

Using S3 for continuous integration testing or in production with Docker⁠

⁠Data storage

When using s3server with a file backend, all data is stored inside the container and is persisted between restarts. You can define the path for data and metadata storage, check our documentation on configuring storage path⁠. When using s3sever with an in-memory backend, all data is lost after you stop the container.

⁠Learn more by reading our documentation⁠ or checking out our website⁠!