103 lines
4.0 KiB
Markdown
103 lines
4.0 KiB
Markdown
# Supported tags and respective `Dockerfile` links
|
|
|
|
- [`2.6.17`, `2.6` (*2.6/Dockerfile*)](https://github.com/docker-library/redis/blob/062335e0a8d20cab2041f25dfff2fbaf58544471/2.6/Dockerfile)
|
|
- [`2.8.19`, `2.8`, `2`, `latest` (*2.8/Dockerfile*)](https://github.com/docker-library/redis/blob/062335e0a8d20cab2041f25dfff2fbaf58544471/2.8/Dockerfile)
|
|
|
|
For more information about this image and its history, please see the [relevant
|
|
manifest file
|
|
(`library/redis`)](https://github.com/docker-library/official-images/blob/master/library/redis)
|
|
in the [`docker-library/official-images` GitHub
|
|
repo](https://github.com/docker-library/official-images).
|
|
|
|
# What is Redis?
|
|
|
|
Redis is an open-source, networked, in-memory, key-value data store with
|
|
optional durability. It is written in ANSI C. The development of Redis has been
|
|
sponsored by Pivotal since May 2013; before that, it was sponsored by VMware.
|
|
According to the monthly ranking by DB-Engines.com, Redis is the most popular
|
|
key-value store. The name Redis means REmote DIctionary Server.
|
|
|
|
> [wikipedia.org/wiki/Redis](https://en.wikipedia.org/wiki/Redis)
|
|
|
|
|
|
|
|
# How to use this image
|
|
|
|
## start a redis instance
|
|
|
|
docker run --name some-redis -d redis
|
|
|
|
This image includes `EXPOSE 6379` (the redis port), so standard container
|
|
linking will make it automatically available to the linked containers (as the
|
|
following examples illustrate).
|
|
|
|
## start with persistent storage
|
|
|
|
docker run --name some-redis -d redis redis-server --appendonly yes
|
|
|
|
If persistence is enabled, data is stored in the `VOLUME /data`, which can be
|
|
used with `--volumes-from some-volume-container` or `-v /docker/host/dir:/data`
|
|
(see [docs.docker volumes](http://docs.docker.com/userguide/dockervolumes/)).
|
|
|
|
For more about Redis Persistence, see
|
|
[http://redis.io/topics/persistence](http://redis.io/topics/persistence).
|
|
|
|
## connect to it from an application
|
|
|
|
docker run --name some-app --link some-redis:redis -d application-that-uses-redis
|
|
|
|
## ... or via `redis-cli`
|
|
|
|
docker run -it --link some-redis:redis --rm redis sh -c 'exec redis-cli -h "$REDIS_PORT_6379_TCP_ADDR" -p "$REDIS_PORT_6379_TCP_PORT"'
|
|
|
|
## Additionally, If you want to use your own redis.conf ...
|
|
|
|
You can create your own Dockerfile that adds a redis.conf from the context into
|
|
/data/, like so.
|
|
|
|
FROM redis
|
|
COPY redis.conf /usr/local/etc/redis/redis.conf
|
|
CMD [ "redis-server", "/usr/local/etc/redis/redis.conf" ]
|
|
|
|
Alternatively, you can specify something along the same lines with `docker run`
|
|
options.
|
|
|
|
docker run -v /myredis/conf/redis.conf:/usr/local/etc/redis/redis.conf --name myredis redis /usr/local/etc/redis/redis.conf
|
|
|
|
Where `/myredis/conf/` is a local directory containing your `redis.conf` file.
|
|
Using this method means that there is no need for you to have a Dockerfile for
|
|
your redis container.
|
|
|
|
# License
|
|
|
|
View [license information](http://redis.io/topics/license) for the software
|
|
contained in this image.
|
|
|
|
# Supported Docker versions
|
|
|
|
This image is officially supported on Docker version 1.5.0.
|
|
|
|
Support for older versions (down to 1.0) is provided on a best-effort basis.
|
|
|
|
# User Feedback
|
|
|
|
## Issues
|
|
|
|
If you have any problems with or questions about this image, please contact us
|
|
through a [GitHub issue](https://github.com/docker-library/redis/issues).
|
|
|
|
You can also reach many of the official image maintainers via the
|
|
`#docker-library` IRC channel on [Freenode](https://freenode.net).
|
|
|
|
## Contributing
|
|
|
|
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](https://github.com/docker-library/redis/issues), 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.
|