Supported tags and respective
rc-buster(opens new window)
rc-alpine3.11(opens new window)
buster(opens new window)
32bit-buster(opens new window)
alpine3.11(opens new window)
4-buster(opens new window)
4-32bit-buster(opens new window)
4-alpine3.11(opens new window)
- Where to get help: the Docker Community Forums (opens new window), the Docker Community Slack (opens new window), or Stack Overflow (opens new window)
- Where to file issues: https://github.com/docker-library/redis/issues
- Maintained by: the Docker Community (opens new window)
- Supported architectures: (more info (opens new window))
amd64(opens new window),
arm32v5(opens new window),
arm32v6(opens new window),
arm32v7(opens new window),
arm64v8(opens new window),
i386(opens new window),
ppc64le(opens new window),
s390x(opens new window)
- Published image artifact details: repo-info repo's
repos/redis/directory (opens new window) (history (opens new window)) (image metadata, transfer size, etc)
- Image updates: official-images PRs with label
library/redis(opens new window) official-images repo's
library/redisfile (opens new window) (history (opens new window))
- Source of this description: docs repo's
redis/directory (opens new window) (history (opens new window))
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 is sponsored by Redis Labs today; before that, it was sponsored by Pivotal and 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.
For the ease of accessing Redis from other containers via Docker networking, the "Protected mode" is turned off by default. This means that if you expose the port outside of your host (e.g., via
docker run), it will be open without a password to anyone. It is highly recommended to set a password (by supplying a config file) if you plan on exposing your Redis instance to the internet. For further information, see the following links about Redis security:
- Redis documentation on security (opens new window)
- Protected mode (opens new window)
- A few things about Redis security by antirez (opens new window)
How to use this image
start a redis instance
$ docker run --name some-redis -d redis
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 (opens new window)).
For more about Redis Persistence, see http://redis.io/topics/persistence.
$ docker run -it --network some-network --rm redis redis-cli -h some-redis
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 redis-server /usr/local/etc/redis/redis.conf
/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.
This variant is not a 32bit image (and will not run on 32bit hardware), but includes Redis compiled as a 32bit binary, especially for users who need the decreased memory requirements associated with that. See "Using 32 bit instances" (opens new window) in the Redis documentation for more information.
- RediSearch (opens new window): Search and Query with Indexing on Redis
- ReJSON (opens new window): Extended JSON processing for Redis
- ReBloom (opens new window): Bloom Filters data type for membership/existence search on Redis
redis images come in many flavors, each designed for a specific use case.
This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
Some of these tags may have names like buster in them. These are the suite code names for releases of Debian (opens new window) and indicate which release the image is based on. If your image needs to install any additional packages beyond what comes with the image, you'll likely want to specify one of these explicitly to minimize breakage when there are new releases of Debian.
This image is based on the popular Alpine Linux project (opens new window), available in the
alpine official image (opens new window). Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
This variant is highly recommended when final image size being as small as possible is desired. The main caveat to note is that it does use musl libc (opens new window) instead of glibc and friends (opens new window), so certain software might run into issues depending on the depth of their libc requirements. However, most software doesn't have an issue with this, so this variant is usually a very safe choice. See this Hacker News comment thread (opens new window) for more discussion of the issues that might arise and some pro/con comparisons of using Alpine-based images.
To minimize image size, it's uncommon for additional related tools (such as
bash) to be included in Alpine-based images. Using this image as a base, add the things you need in your own Dockerfile (see the
alpine image description (opens new window) for examples of how to install packages if you are unfamiliar).
View license information (opens new window) for the software contained in this image.
As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).
Some additional license information which was able to be auto-detected might be found in the
redis/ directory (opens new window).
As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.