Public | Automated Build

Last pushed: 6 days ago
Short Description
Official OpenIO SDS Docker image.
Full Description

openio/sds Dockerfile

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

How to use this image

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

Keep it simple

By default, start a simple namespace listening on 127.0.0.1 inside the container.
An Openstack Swift proxy with the Swift3 middleware is available, with TempAuth authentication system and default credentials set to demo:demo and password DEMO_PASS.

# docker run -ti --tty openio/sds

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 cant 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=192.168.56.101 --net=host openio/sds

Change the Openstack Swift default credentials:

# docker run -ti --tty -e OPENIO_IFDEV=enp0s8 --net=host -e SWIFT_CREDENTIALS="myproject:myuser:mypassord:.admin" openio/sds

Bind the Openstack Swift/Swift3 proxy port to you host:

# docker run -ti --tty -p 192.168.56.101:6007:6007 openio/sds

Setting the default credentials to test Openstack Swift functionnal tests:

# docker run -ti --tty -p 192.168.56.101:6007:6007 -e SWIFT_CREDENTIALS="admin:admin:admin:.admin .reseller_admin,test2:tester2:testing2:.admin,test5:tester5:testing5:service,test:tester:testing:.admin,test:tester3:testing" openio/sds

Documentation

To test with different object storage clients:

Docker Pull Command
Owner
openio
Source Repository

Comments (0)