d11wtq/redis repository overview

⁠Testing

To test that the container works, start it without any special options, then make sure you can talk to it on port 6379.

-bash$ docker run -d -p 6379:6379 d11wtq/redis
abcdef1234567890abcdef1234567890abcdef1234567890ab

-bash$ nc -z localhost 6379
Connection to localhost port 6379 [tcp] succeeded!

⁠Configuration

This is a very simple container. Redis stores its data under /redis/data and uses an extremely minimal configuration file from /redis/redis.conf.

It is expected that you mount /redis/data as a volume if you require long-lived persistence on the host.

Redis runs under the user 'default'. Logs are written to stdout/stderr.

You may change the configuration by mounting /redis/redis.conf (docker allows you to mount files with -v).

⁠Example Usage

The following shows an example of running redis with data persisted on the host.

-bash$ docker run -d \
>   --name redis \
>   -v $(pwd)/data:/redis/data \
>   d11wtq/redis
abcdef1234567890abcdef1234567890abcdef1234567890ab
-bash$

The shared volume data/ is initially empty, but will be initialized by the container.

⁠Client Access

If you need to try something in the redis-cli client, the intended way to do this is to use two containers in a client-server setup. Start the server container with a name, then start a second container linking to that name, but running 'bash', or 'redis-cli' instead of the default command.

Connecting a client to the above server would look like this:

-bash$ docker run -ti \
>   --link redis:server \
>   d11wtq/redis \
>   redis-cli -h server

server:6379>