This image is updated via pull requests to the touchifyapp/docker-riak-kv GitHub repo.
Riak® KV: A distributed NoSQL key/value database.
Riak® KV is a distributed NoSQL key/value database with advanced local and multi-cluster replication that guarantees reads and writes even in the event of hardware failures or network partitions..
# Run a Riak KV server
# Each server exposes multiple ports
# 8087 is for Protocol Buffer clients.
# 8098 is for HTTP clients.
# use -p or -P as needed.
$ docker run -d -P --name riak-kv touchify/riak-kv
# Create a network overlay
$ docker network create -d overlay databases
# Start a Riak KV cluster.
# Use RIAK_SERVICE_NAME variable to configure the cluster service name.
# WARNING: can't start multiple replicas
$ docker service create \
$ --name riak-kv-cluster \
$ --network databases \
$ --env RIAK_SERVICE_NAME=riak-kv-cluster \
$ touchify/riak-kv
# Scale a Riak KV cluster.
# WARNING: only scale one by one.
# WARNING: Can't scale down.
$ docker service scale riak-kv-cluster=2
All .dt files in /etc/riak/schemas/ are parsed during startup and added to Riak KV.
- The filename will be the bucket type name.
- The file content will be the bucket type definition (in JSON format).
Cluster Options:
RIAK_SERVICE_NAME For use in Docker 1.12 in Swarm mode.
Should equal to Docker service name in Swarm.
Used to configure the Riak KV cluster.
RIAK_CLUSTER_NAME Set the Riak KV cluster name.
Configurations:
RIAK_BACKEND Set the Riak backend technology (`bitcask` or `leveldb`)
RIAK_STRONG_CONSISTENCY Enable or disable Riak strong consistency (`on` or `off`).
View license information for the software contained in this image.
This image is officially supported on Docker version 1.12+.
Please see the Docker installation documentation for details on how to upgrade your Docker daemon.
Documentation for this image is stored in the touchifyapp/docker-riak-kv GitHub repo.
Be sure to familiarize yourself with the repository's README.md file before attempting a pull request.
If you have any problems with or questions about this image, please contact us through a GitHub issue.
You are invited to contribute new features, fixes, or updates, large or small; we are always thrilled to receive pull requests, and do our best to process them as fast as we can.
Before you start to code, we recommend discussing your plans through a GitHub issue, especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.