Docker Image

This Docker image provides an easy way to run an OPENIO namespace. It deploys and configure a simple non-replicated namespace in a single container.

OpenIO SDS service discovering and resolution relies on IPs, meaning that you can’t change service IPs after they have been registered to the cluster. By default, Docker networking may change you IP when you container restarts which is not compatible with OpenIO SDS at the moment.


First, pull the OpenIO Docker image from the Docker Hub:

# docker pull openio/sds

By default, start a simple namespace listening on inside the container using docker run:

# docker run -ti --tty openio/sds

You are now able to manipulate your namespace inside your container using the OpenIO End User CLI. For example, put an object :

# echo 'Hello OpenIO!' > test.txt

# openio object create MY_CONTAINER test.txt --oio-ns OPENIO --oio-account MYACCOUNT

Deploy the S3/Swift gateway

You can launch the OpenIO docker image with our S3 and Swift gateway embedded, and map its port (6007) to access to it remotely:

Launching the container with the port mapping:

# docker run -ti --tty -p openio/sds

The S3 and Swift gateway is now accessible on

Using Swift gateway

First install python-swiftclient

# yum install python-swiftclient

Then, you can use the swift APIs:

# swift -A -U demo:demo -K DEMO_PASS stat

Using S3 gateway

First install awscli

# yum install awscli

Then, set your credentials in the following configuration file ~/.aws/credentials:

s3 =
    signature_version = s3

Finally you can put your first object:

# aws --endpoint-url --no-verify-ssl s3 cp /etc/localtime s3://bucket1

Using host network interface

You can start an instance using Docker host mode networking, it allows you to access the services outside your container. You can specify the interface or the IP you want to use.

Setting the interface:

# docker run -ti --tty -e OPENIO_IFDEV=enp0s8 --net=host openio/sds

Specifying the IP:

# docker run -ti --tty -e OPENIO_IPADDR= --net=host openio/sds