fake-s3

We're deep in forktown here. Ok so here's what happened:

1. jubos created the original, amazing fake-s3
2. In order to fix this bug, saltzmanjoelh forked it
3. lphoward maintains a Dockerfile for the original S3: github, dockerhub
4. camjackson needed a Dockerised, bug-fixed version of fake-s3, so camjackson forked #3, and modified the Dockerfile to point at #2 instead of #1
5. We needed delete-object functionality in fake-s3 as well as the bug fix made by saltzmanjoelh, so we needed to make our own fork of fake-s3 off saltzmanjoelh and then fork this repo in order to point at the different repo

Dockerfile for kuracloud/fake-s3 on Docker Hub.

Deploys fake-s3 in a Docker container.

To create a deployment:

    docker run --name my_s3 -d kuracloud/fake-s3

Service exposed on port 4569. Credentials are ignored. See fake-s3 README for details/limitations.

If you want fake-s3 to be exposed on your Docker host on port 4569, then

    docker run --name my_s3 -p 4569:4569 -d kuracloud/fake-s3

If you want the container to use a volume, then

    docker run --name my_s3 -v /fakes3_root -d kuracloud/fake-s3

The fake-s3 root directory will then be added as a volume on the Docker host. To get the volume

    docker inspect --format "{{range .Mounts}}{{.Source}}{{end}}" my_s3