arm64v8/nginx Docker Image
Nginx的官方构建版本是一款高性能的HTTP和反向代理服务器,同时也可作为IMAP/POP3/SMTP代理服务器,其官方版本经过严格测试,包含稳定的核心功能及多种扩展模块,广泛应用于网站部署、负载均衡、动静分离等场景,凭借高效的并发处理能力和低资源消耗,成为全球范围内主流的Web服务器解决方案之一。
Note: this is the "per-architecture" repository for the arm64v8 builds of https://hub.docker.com/_/nginx -- 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.
Quick reference
-
Maintained by:
https://github.com/nginx/docker-nginx -
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
Supported tags and respective Dockerfile links
-
https://github.com/nginx/docker-nginx/blob/6fabb4c960a02a1e576d2789974c45f4cd2aa854/mainline/debian/Dockerfile
-
https://github.com/nginx/docker-nginx/blob/6fabb4c960a02a1e576d2789974c45f4cd2aa854/mainline/debian-perl/Dockerfile
-
https://github.com/nginx/docker-nginx/blob/6fabb4c960a02a1e576d2789974c45f4cd2aa854/mainline/debian-otel/Dockerfile
-
https://github.com/nginx/docker-nginx/blob/6fabb4c960a02a1e576d2789974c45f4cd2aa854/mainline/alpine/Dockerfile
-
https://github.com/nginx/docker-nginx/blob/6fabb4c960a02a1e576d2789974c45f4cd2aa854/mainline/alpine-perl/Dockerfile
-
https://github.com/nginx/docker-nginx/blob/6fabb4c960a02a1e576d2789974c45f4cd2aa854/mainline/alpine-slim/Dockerfile
-
https://github.com/nginx/docker-nginx/blob/6fabb4c960a02a1e576d2789974c45f4cd2aa854/mainline/alpine-otel/Dockerfile
-
https://github.com/nginx/docker-nginx/blob/4b9f658be76820b24e4ef4605413a5c08707a512/stable/debian/Dockerfile
-
https://github.com/nginx/docker-nginx/blob/4b9f658be76820b24e4ef4605413a5c08707a512/stable/debian-perl/Dockerfile
-
https://github.com/nginx/docker-nginx/blob/4b9f658be76820b24e4ef4605413a5c08707a512/stable/debian-otel/Dockerfile
-
https://github.com/nginx/docker-nginx/blob/4b9f658be76820b24e4ef4605413a5c08707a512/stable/alpine/Dockerfile
-
https://github.com/nginx/docker-nginx/blob/4b9f658be76820b24e4ef4605413a5c08707a512/stable/alpine-perl/Dockerfile
-
https://github.com/nginx/docker-nginx/blob/4b9f658be76820b24e4ef4605413a5c08707a512/stable/alpine-slim/Dockerfile
-
https://github.com/nginx/docker-nginx/blob/4b9f658be76820b24e4ef4605413a5c08707a512/stable/alpine-otel/Dockerfile
Quick reference (cont.)
-
Where to file issues:
https://github.com/nginx/docker-nginx/issues?q=is:issue+is:pr -
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)
What is 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
How to use this image
Hosting some simple static content
console$ docker run --name some-nginx -v /some/content:/usr/share/nginx/html:ro -d arm64v8/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 arm64v8/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
Exposing external port
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.
Customize configuration
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 arm64v8/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 http://nginx.org/en/docs/ (specifically the http://nginx.org/en/docs/beginners_guide.html#conf_structure).
Mount your configuration file
console$ docker run --name my-custom-nginx-container -v /host/path/nginx.conf:/etc/nginx/nginx.conf:ro -d arm64v8/nginx
Build a new image with your configuration file
dockerfileFROM arm64v8/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
Using environment variables in arm64v8/nginx configuration (new in 1.19)
Out-of-the-box, arm64v8/nginx doesn't support environment variables inside most configuration blocks. But this image has a function, which will extract environment variables before arm64v8/nginx starts.
Here is an example using compose.yaml:
yamlweb: image: arm64v8/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- A directory which contains template files (default:
/etc/nginx/templates) - When this directory doesn't exist, this function will do nothing about template processing.
- A directory which contains template files (default:
NGINX_ENVSUBST_TEMPLATE_SUFFIX- A suffix of template files (default:
.template) - This function only processes the files whose name ends with this suffix.
- A suffix of template files (default:
NGINX_ENVSUBST_OUTPUT_DIR- A directory where the result of executing envsubst is output (default:
/etc/nginx/conf.d) - The output filename is the template filename with the suffix removed.
- ex.)
/etc/nginx/templates/default.conf.templatewill be output with the filename/etc/nginx/conf.d/default.conf.
- ex.)
- This directory must be writable by the user running a container.
- A directory where the result of executing envsubst is output (default:
NGINX_ENVSUBST_FILTER- A regular expression to filter environment variable names passed to
envsubst(default: empty string) - When set, only variables whose names match this pattern are available for substitution.
- A regular expression to filter environment variable names passed to
Running arm64v8/nginx in read-only mode
To run arm64v8/nginx in read-only mode, you will need to mount a Docker volume to every location where arm64v8/nginx writes information. The default arm64v8/nginx configuration requires write access to /var/cache/nginx and /var/run. This can be easily accomplished by running arm64v8/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 arm64v8/nginx to write to other locations, simply add more volume mounts to those locations.
Running nginx in debug mode
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 arm64v8/nginx nginx-debug -g 'daemon off;'
Similar configuration in compose.yaml may look like this:
yamlweb: image: arm64v8/nginx volumes: - ./nginx.conf:/etc/nginx/nginx.conf:ro command: [nginx-debug, '-g', 'daemon off;']
Entrypoint quiet logs
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 arm64v8/nginx
User and group id
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)
Running arm64v8/nginx as a non-root user
It is possible to run the image as a less privileged arbitrary UID/GID. This, however, requires modification of arm64v8/nginx configuration to use directories writeable by that specific UID/GID pair:
console$ docker run -d -v $PWD/nginx.conf:/etc/nginx/nginx.conf arm64v8/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.
Image Variants
The arm64v8/nginx images come in many flavors, each designed for a specific use case.
arm64v8/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 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/nginx:<version>-perl / arm64v8/nginx:<version>-alpine-perl
Starting with arm64v8/nginx:1.13.0 / mainline and arm64v8/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.
arm64v8/nginx:<version>-alpine
This 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).
arm64v8/nginx:<version>-slim
This image does not contain the common packages contained in the default tag and only contains the minimal packages needed to run arm64v8/nginx. Unless you are working in an environment where only the arm64v8/nginx image will be deployed and you have space constraints, we highly recommend using the default image of this repository.
License
View http://nginx.org/LICENSE 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.
更多相关 Docker 镜像与资源
以下是 arm64v8/nginx 相关的常用 Docker 镜像,适用于 反向代理、负载均衡、静态资源服务 等不同场景:
镜像拉取方式
您可以使用以下命令拉取该镜像。请将 <标签> 替换为具体的标签版本。如需查看所有可用标签版本,请访问 标签列表页面。
DockerHub 原生拉取命令
用户好评
来自真实用户的反馈,见证轩辕镜像的优质服务