
如果你使用 DeepSeek、元宝 AI、Copilot、ChatGPT 等 AI 工具,协助配置轩辕镜像、编写 docker pull 命令、修改 Docker Compose 镜像地址、配置镜像加速、排查镜像拉取失败、分析报错日志等问题,请先让 AI 阅读并遵守轩辕镜像的规则文档。
只需在 AI 对话中先发送下面这句话即可:
请先完整阅读并严格遵守以下文档中的全部规则与要求:
https://xuanyuan.cloud/agents.md
在未充分阅读并理解该文档前,不要生成任何命令、配置、修改建议、故障排查方案或技术回答。后续所有输出都必须严格以该文档中的规范为最高优先级执行。查看 agents.md 用法指南与完整示范。国内用户首推 元宝 AI、DeepSeek 的深度思考模式,不推荐豆包 AI;Cursor 等编辑器可在对话 @ 该链接,或加入 User Rules。 若 AI 无法访问外链,可 打开说明文档 复制全文粘贴。文档会随站点更新,复制内容可能过期,建议定期检查。
Note: this is the "per-architecture" repository for the arm64v8 builds of https://hub.docker.com/_/redis -- for more information, see https://github.com/docker-library/official-images#architectures-other-than-amd64 and https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what.
Maintained by:
https://redis.io/
Where to get help:
https://dockr.ly/comm-slack, Server Fault, https://unix.stackexchange.com/help/on-topic, or https://stackoverflow.com/help/on-topic
Dockerfile linkshttps://github.com/redis/docker-library-redis/blob/0a24b09f88a6cb8feaf130d4eca7bd6b9b4c73a3/debian/Dockerfile
https://github.com/redis/docker-library-redis/blob/0a24b09f88a6cb8feaf130d4eca7bd6b9b4c73a3/alpine/Dockerfile
https://github.com/redis/docker-library-redis/blob/b675641c81d9f476e614aee4a6606365548bae41/debian/Dockerfile
https://github.com/redis/docker-library-redis/blob/b675641c81d9f476e614aee4a6606365548bae41/alpine/Dockerfile
https://github.com/redis/docker-library-redis/blob/8bf384f30957c89ea17a1fd6e5f34ed31065f84b/debian/Dockerfile
https://github.com/redis/docker-library-redis/blob/8bf384f30957c89ea17a1fd6e5f34ed31065f84b/alpine/Dockerfile
https://github.com/redis/docker-library-redis/blob/cc3829e8d874f31c8d50ee1e7a81f283eaa9688a/debian/Dockerfile
https://github.com/redis/docker-library-redis/blob/cc3829e8d874f31c8d50ee1e7a81f283eaa9688a/alpine/Dockerfile
https://github.com/redis/docker-library-redis/blob/3769a841048d940966635f8f59471f3d350707bf/debian/Dockerfile
https://github.com/redis/docker-library-redis/blob/3769a841048d940966635f8f59471f3d350707bf/alpine/Dockerfile
https://github.com/redis/docker-library-redis/blob/31c68732e7311d95e4c833b8fa50aa561ced577f/debian/Dockerfile
https://github.com/redis/docker-library-redis/blob/31c68732e7311d95e4c833b8fa50aa561ced577f/alpine/Dockerfile
https://github.com/redis/docker-library-redis/blob/976a7de4cd78b6a201b4a3a5ac49cd9c8e3e583f/debian/Dockerfile
https://github.com/redis/docker-library-redis/blob/976a7de4cd78b6a201b4a3a5ac49cd9c8e3e583f/alpine/Dockerfile
https://github.com/redis/docker-library-redis/blob/70d903a68609970bf9a66181cdc59d0fc1ebc885/debian/Dockerfile
https://github.com/redis/docker-library-redis/blob/70d903a68609970bf9a66181cdc59d0fc1ebc885/alpine/Dockerfile
Where to file issues:
https://github.com/redis/docker-library-redis/issues?q=
Supported architectures: (https://github.com/docker-library/official-images#architectures-other-than-amd64)
https://hub.docker.com/r/amd64/redis/, https://hub.docker.com/r/arm32v5/redis/, https://hub.docker.com/r/arm32v6/redis/, https://hub.docker.com/r/arm32v7/redis/, https://hub.docker.com/r/arm64v8/redis/, https://hub.docker.com/r/i386/redis/, https://hub.docker.com/r/ppc64le/redis/, https://hub.docker.com/r/riscv64/redis/, https://hub.docker.com/r/s390x/redis/
Published image artifact details:
https://github.com/docker-library/repo-info/blob/master/repos/redis (https://github.com/docker-library/repo-info/commits/master/repos/redis)
(image metadata, transfer size, etc)
Image updates:
https://github.com/docker-library/official-images/issues?q=label%3Alibrary%2Fredis
https://github.com/docker-library/official-images/blob/master/library/redis (https://github.com/docker-library/official-images/commits/master/library/redis)
Source of this description:
https://github.com/docker-library/docs/tree/master/redis (https://github.com/docker-library/docs/commits/master/redis)
Redis is the world’s fastest data platform. It provides cloud and on-prem solutions for caching, vector search, and NoSQL databases that seamlessly fit into any tech stack—making it simple for digital customers to build, scale, and deploy the fast apps our world runs on.
https://redis.io
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 -p on 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:
By default, the Redis Docker image drops privileges by switching to the redis user and removing unnecessary capabilities. This step is skipped if Docker is run with the --user option or if you set the SKIP_DROP_PRIVS=1 (since 8.0.2) environment variable.
Note: Using SKIP_DROP_PRIVS is not recommended, as it reduces the container's security.
console$ docker run --name some-redis -d arm64v8/redis
console$ docker run --name some-redis -d arm64v8/redis redis-server --save 60 1 --loglevel warning
There are several different persistence strategies to choose from. This one will save a snapshot of the DB every 60 seconds if at least 1 write operation was performed (it will also lead to more logs, so the loglevel option may be desirable). 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 https://docs.docker.com/engine/tutorials/dockervolumes/).
For more about Redis persistence, see https://redis.io/docs/latest/operate/oss_and_stack/management/persistence/.
Redis will attempt to correct the ownership and permissions of the data and configuration (since 8.0.2) directories and files if they are not set correctly. This adjustment is only performed in basic, default scenarios to avoid interfering with custom or user-specific configurations.
You can skip this step by setting the SKIP_FIX_PERMS=1(since 8.0.2) environment variable.
If you prefer to handle file permissions yourself, you can use a docker run command to set the correct ownership on mounted volumes. For example:
console$ docker run --rm -v /your/host/path:/data arm64v8/redis chown -R redis:redis /data
redis-cliconsole$ docker run -it --network some-network --rm arm64v8/redis redis-cli -h some-redis
You can create your own Dockerfile that adds a redis.conf from the context into /data/, like so.
dockerfileFROM arm64v8/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.
console$ docker run -v /myredis/conf:/usr/local/etc/redis --name myredis arm64v8/redis redis-server /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.
The mapped directory should be writable, as depending on the configuration and mode of operation, Redis may need to create additional configuration files or rewrite existing ones.
The arm64v8/redis images come in many flavors, each designed for a specific use case.
arm64v8/redis:<version>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 bookworm or trixie in them. These are the suite code names for releases of https://wiki.debian.org/DebianReleases 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.
arm64v8/redis:<version>-alpineThis image is based on the popular [***] available in https://hub.docker.com/_/alpine. Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
This variant is useful when final image size being as small as possible is your primary concern. The main caveat to note is that it does use https://musl.libc.org instead of https://www.etalabs.net/compare_libcs.html, so software will often run into issues depending on the depth of their libc requirements/assumptions. See this Hacker News comment thread 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 git or 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 https://hub.docker.com/_/alpine/ for examples of how to install packages if you are unfamiliar).
Starting with Redis 8.0, Redis follows a tri-licensing model with the choice of the https://redis.io/legal/rsalv2-agreement/, https://redis.io/legal/server-side-public-license-sspl/, or the https://opensource.org/license/agpl-v3. Prior versions of Redis (<=7.2.4) are licensed under https://opensource.org/license/bsd-3-clause, and Redis 7.4.x-7.8.x are licensed under the dual https://redis.io/legal/rsalv2-agreement/ or https://redis.io/legal/server-side-public-license-sspl/ license.
Please also view the https://redis.io/legal/licenses/ and the https://redis.io/legal/trademark-policy/.
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 https://github.com/docker-library/repo-info/tree/master/repos/redis.
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.
以下是 arm64v8/redis 相关的常用 Docker 镜像,适用于 缓存、高可用、数据分析 等不同场景:
您可以使用以下命令拉取该镜像。请将 <标签> 替换为具体的标签版本。如需查看所有可用标签版本,请访问 标签列表页面。
来自真实用户的反馈,见证轩辕镜像的优质服务