
如果你用 DeepSeek、元宝AI、Copilot 等 AI 代为编写轩辕镜像的 docker pull、修改 compose 镜像地址,或排查拉取失败等问题,请让 AI 先读规则再动手,只要在 AI 对话里直接发送下面这句话即可:
生成 docker pull、修改 compose 的 image,或排查拉取失败前,请先阅读并严格遵守 https://xuanyuan.cloud/agents.md 中的规则。国内用户首推 元宝 AI、DeepSeek 的深度思考模式,不推荐豆包 AI;Cursor 等编辑器可在对话 @ 该链接,或加入 User Rules。 若 AI 无法访问外链,可 打开说明文档 复制全文粘贴。文档会随站点更新,复制内容可能过期,建议定期检查。
Maintained by:
https://github.com/nginxinc/docker-nginx
Where to get help:
the Docker Community Slack, Server Fault, Unix & Linux, or Stack Overflow
Dockerfile linkshttps://github.com/nginx/docker-nginx/blob/3375edc7170bc7b7da708c1c658706eb5355e099/mainline/debian/Dockerfile
https://github.com/nginx/docker-nginx/blob/3375edc7170bc7b7da708c1c658706eb5355e099/mainline/debian-perl/Dockerfile
https://github.com/nginx/docker-nginx/blob/3375edc7170bc7b7da708c1c658706eb5355e099/mainline/debian-otel/Dockerfile
https://github.com/nginx/docker-nginx/blob/3375edc7170bc7b7da708c1c658706eb5355e099/mainline/alpine/Dockerfile
https://github.com/nginx/docker-nginx/blob/3375edc7170bc7b7da708c1c658706eb5355e099/mainline/alpine-perl/Dockerfile
https://github.com/nginx/docker-nginx/blob/3375edc7170bc7b7da708c1c658706eb5355e099/mainline/alpine-slim/Dockerfile
https://github.com/nginx/docker-nginx/blob/3375edc7170bc7b7da708c1c658706eb5355e099/mainline/alpine-otel/Dockerfile
https://github.com/nginx/docker-nginx/blob/3375edc7170bc7b7da708c1c658706eb5355e099/stable/debian/Dockerfile
https://github.com/nginx/docker-nginx/blob/3375edc7170bc7b7da708c1c658706eb5355e099/stable/debian-perl/Dockerfile
https://github.com/nginx/docker-nginx/blob/3375edc7170bc7b7da708c1c658706eb5355e099/stable/debian-otel/Dockerfile
https://github.com/nginx/docker-nginx/blob/3375edc7170bc7b7da708c1c658706eb5355e099/stable/alpine/Dockerfile
https://github.com/nginx/docker-nginx/blob/3375edc7170bc7b7da708c1c658706eb5355e099/stable/alpine-perl/Dockerfile
https://github.com/nginx/docker-nginx/blob/3375edc7170bc7b7da708c1c658706eb5355e099/stable/alpine-slim/Dockerfile
https://github.com/nginx/docker-nginx/blob/3375edc7170bc7b7da708c1c658706eb5355e099/stable/alpine-otel/Dockerfile
Where to file issues:
https://github.com/nginxinc/docker-nginx/issues?q=
Supported architectures: (https://github.com/docker-library/official-images#architectures-other-than-amd64)
https://hub.docker.com/r/amd64/nginx/, https://hub.docker.com/r/arm32v5/nginx/, https://hub.docker.com/r/arm32v6/nginx/, https://hub.docker.com/r/arm32v7/nginx/, https://hub.docker.com/r/arm64v8/nginx/, https://hub.docker.com/r/i386/nginx/, https://hub.docker.com/r/ppc64le/nginx/, https://hub.docker.com/r/riscv64/nginx/, https://hub.docker.com/r/s390x/nginx/
Published image artifact details:
https://github.com/docker-library/repo-info/blob/master/repos/nginx (https://github.com/docker-library/repo-info/commits/master/repos/nginx)
(image metadata, transfer size, etc)
Image updates:
https://github.com/docker-library/official-images/issues?q=label%3Alibrary%2Fnginx
https://github.com/docker-library/official-images/blob/master/library/nginx (https://github.com/docker-library/official-images/commits/master/library/nginx)
Source of this description:
https://github.com/docker-library/docs/tree/master/nginx (https://github.com/docker-library/docs/commits/master/nginx)
Nginx (pronounced "engine-x") is an open source reverse proxy server for HTTP, HTTPS, SMTP, POP3, and IMAP protocols, as well as a load ***, HTTP cache, and a web server (origin server). The nginx project started with a strong focus on high concurrency, high performance and low memory usage. It is licensed under the 2-clause BSD-like license and it runs on Linux, BSD variants, Mac OS X, Solaris, AIX, HP-UX, as well as on other *nix flavors. It also has a proof of concept port for Microsoft Windows.
***.org/wiki/Nginx
!https://raw.githubusercontent.com/docker-library/docs/01c***b2fe592c1f93a13b4e289ada0e3a1/nginx/logo.png
console$ docker run --name some-nginx -v /some/content:/usr/share/nginx/html:ro -d nginx
Alternatively, a simple Dockerfile can be used to generate a new image that includes the necessary content (which is a much cleaner solution than the bind mount above):
dockerfileFROM nginx COPY static-html-directory /usr/share/nginx/html
Place this file in the same directory as your directory of content ("static-html-directory"), then run these commands to build and start your container:
console$ docker build -t some-content-nginx . $ docker run --name some-nginx -d some-content-nginx
console$ docker run --name some-nginx -d -p 8080:80 some-content-nginx
Then you can hit http://localhost:8080 or http://host-ip:8080 in your browser.
You can mount your configuration file, or build a new image with it.
If you wish to adapt the default configuration, use something like the following to get it from a running nginx container:
console$ docker run --rm --entrypoint=cat nginx /etc/nginx/nginx.conf > /host/path/nginx.conf
And then edit /host/path/nginx.conf in your host file system.
For information on the syntax of the nginx configuration files, see the official documentation (specifically the Beginner's Guide).
console$ docker run --name my-custom-nginx-container -v /host/path/nginx.conf:/etc/nginx/nginx.conf:ro -d nginx
dockerfileFROM nginx COPY nginx.conf /etc/nginx/nginx.conf
If you add a custom CMD in the Dockerfile, be sure to include -g daemon off; in the CMD in order for nginx to stay in the foreground, so that Docker can track the process properly (otherwise your container will stop immediately after starting)!
Then build the image with docker build -t custom-nginx . and run it as follows:
console$ docker run --name my-custom-nginx-container -d custom-nginx
Out-of-the-box, nginx doesn't support environment variables inside most configuration blocks. But this image has a function, which will extract environment variables before nginx starts.
Here is an example using compose.yaml:
yamlweb: image: nginx volumes: - ./templates:/etc/nginx/templates ports: - "8080:80" environment: - NGINX_HOST=foobar.com - NGINX_PORT=80
By default, this function reads template files in /etc/nginx/templates/*.template and outputs the result of executing envsubst to /etc/nginx/conf.d.
So if you place templates/default.conf.template file, which contains variable references like this:
listen ${NGINX_PORT};
outputs to /etc/nginx/conf.d/default.conf like this:
listen 80;
This behavior can be changed via the following environment variables:
NGINX_ENVSUBST_TEMPLATE_DIR
/etc/nginx/templates)NGINX_ENVSUBST_TEMPLATE_SUFFIX
.template)NGINX_ENVSUBST_OUTPUT_DIR
/etc/nginx/conf.d)/etc/nginx/templates/default.conf.template will be output with the filename /etc/nginx/conf.d/default.conf.To run nginx in read-only mode, you will need to mount a Docker volume to every location where nginx writes information. The default nginx configuration requires write access to /var/cache/nginx and /var/run. This can be easily accomplished by running nginx as follows:
console$ docker run -d -p 80:80 --read-only -v $(pwd)/nginx-cache:/var/cache/nginx -v $(pwd)/nginx-pid:/var/run nginx
If you have a more advanced configuration that requires nginx to write to other locations, simply add more volume mounts to those locations.
Images since version 1.9.8 come with nginx-debug binary that produces verbose output when using higher log levels. It can be used with simple CMD substitution:
console$ docker run --name my-nginx -v /host/path/nginx.conf:/etc/nginx/nginx.conf:ro -d nginx nginx-debug -g 'daemon off;'
Similar configuration in compose.yaml may look like this:
yamlweb: image: nginx volumes: - ./nginx.conf:/etc/nginx/nginx.conf:ro command: [nginx-debug, '-g', 'daemon off;']
Since version 1.19.0, a verbose entrypoint was added. It provides information on what's happening during container startup. You can silence this output by setting environment variable NGINX_ENTRYPOINT_QUIET_LOGS:
console$ docker run -d -e NGINX_ENTRYPOINT_QUIET_LOGS=1 nginx
Since 1.17.0, both alpine- and debian-based images variants use the same user and group ids to drop the privileges for worker processes:
console$ id uid=101(nginx) gid=101(nginx) groups=101(nginx)
It is possible to run the image as a less privileged arbitrary UID/GID. This, however, requires modification of nginx configuration to use directories writeable by that specific UID/GID pair:
console$ docker run -d -v $PWD/nginx.conf:/etc/nginx/nginx.conf nginx
where nginx.conf in the current directory should have the following directives re-defined:
nginxpid /tmp/nginx.pid;
And in the http context:
nginxhttp { client_body_temp_path /tmp/client_temp; proxy_temp_path /tmp/proxy_temp_path; fastcgi_temp_path /tmp/fastcgi_temp; uwsgi_temp_path /tmp/uwsgi_temp; scgi_temp_path /tmp/scgi_temp; ... }
Alternatively, check out the official https://hub.docker.com/r/nginxinc/nginx-unprivileged.
The nginx images come in many flavors, each designed for a specific use case.
nginx:<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 trixie in them. These are the suite code names for releases of Debian 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.
nginx:<version>-perl / nginx:<version>-alpine-perlStarting with nginx:1.13.0 / mainline and nginx:1.12.0 / stable, the perl module has been removed from the default images. A separate -perl tag variant is available if you wish to use the perl module.
nginx:<version>-alpineThis image is based on the popular Alpine Linux project, 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 musl libc instead of glibc and friends, 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).
nginx:<version>-slimThis image does not contain the common packages contained in the default tag and only contains the minimal packages needed to run nginx. Unless you are working in an environment where only the nginx image will be deployed and you have space constraints, we highly recommend using the default image of this repository.
View license information 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 https://github.com/docker-library/repo-info/tree/master/repos/nginx.
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.
以下是 nginx 相关的常用 Docker 镜像,适用于 反向代理、负载均衡、静态资源服务 等不同场景:
您可以使用以下命令拉取该镜像。请将 <标签> 替换为具体的标签版本。如需查看所有可用标签版本,请访问 标签列表页面。

探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式
通过 Docker 登录认证访问私有仓库
发给 Cursor、ChatGPT、豆包等 AI 的说明文档
无需登录使用专属域名
Kubernetes 集群配置 Containerd
K3s 轻量级 Kubernetes 镜像加速
VS Code Dev Containers 配置
Podman 容器引擎配置
HPC 科学计算容器配置
ghcr、Quay、nvcr 等镜像仓库
Harbor Proxy Repository 对接专属域名
Portainer Registries 加速拉取
Nexus3 Docker Proxy 内网缓存
需要其他帮助?请查看我们的 常见问题Docker 镜像访问常见问题解答 或 提交工单
docker search 限制
站内搜不到镜像
离线 save/load
插件要用 plugin install
WSL 拉取慢
安全与 digest
新手拉取配置
镜像合规机制
不支持 push
manifest unknown
no matching manifest(架构)
invalid tar header(解压)
Schema 1 已废弃
406 OCI index
422 Unknown
400 TAG_INVALID
TLS 证书失败
DNS 超时
域名连通性排查
410 Gone 排查
402 与流量用尽
401 认证失败
429 限流
D-Bus 凭证提示
413 与超大单层
来自真实用户的反馈,见证轩辕镜像的优质服务