[READY] Fix S3 hostname issue

When running the [fake-s3](https://www.github.com/stevenjack/fake-s3) inside a docker container, the host resolution is incorrect as it tries to match the the ip of the host accessing the service against the ip that the service was run on. The issue here is that the IP reported to the container is that of the boot2docker box (or any other VM running docker), and it causes the gem to work incorrectly when using the `as_tree` functionality of the ruby-sdk and most likely other SDK's that implement the prefix functionality.