**Note:** this is the "per-architecture" repository for the `arm32v5` builds of [the `nginx` official image](https://hub.docker.com/_/nginx) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what). # Quick reference - **Maintained by**: [the NGINX Docker Maintainers](https://github.com/nginxinc/docker-nginx) - **Where to get help**: [the Docker Community Slack](https://dockr.ly/comm-slack), [Server Fault](https://serverfault.com/help/on-topic), [Unix & Linux](https://unix.stackexchange.com/help/on-topic), or [Stack Overflow](https://stackoverflow.com/help/on-topic) # Supported tags and respective `Dockerfile` links - [`1.29.3`, `mainline`, `1`, `1.29`, `latest`, `1.29.3-trixie`, `mainline-trixie`, `1-trixie`, `1.29-trixie`, `trixie`](https://github.com/nginx/docker-nginx/blob/e4d5453581d9d3618f77c4aeccf2e6171a1cd6ff/mainline/debian/Dockerfile) - [`1.29.3-perl`, `mainline-perl`, `1-perl`, `1.29-perl`, `perl`, `1.29.3-trixie-perl`, `mainline-trixie-perl`, `1-trixie-perl`, `1.29-trixie-perl`, `trixie-perl`](https://github.com/nginx/docker-nginx/blob/e4d5453581d9d3618f77c4aeccf2e6171a1cd6ff/mainline/debian-perl/Dockerfile) - [`1.28.0`, `stable`, `1.28`, `1.28.0-bookworm`, `stable-bookworm`, `1.28-bookworm`](https://github.com/nginx/docker-nginx/blob/9b549fdf936778810dbe95a4813899c60444ef1c/stable/debian/Dockerfile) - [`1.28.0-perl`, `stable-perl`, `1.28-perl`, `1.28.0-bookworm-perl`, `stable-bookworm-perl`, `1.28-bookworm-perl`](https://github.com/nginx/docker-nginx/blob/7f1d49f6f222f7e588a9066fd53a0ce43c3466a5/stable/debian-perl/Dockerfile) # Quick reference (cont.) - **Where to file issues**: [https://github.com/nginxinc/docker-nginx/issues](https://github.com/nginxinc/docker-nginx/issues?q=) - **Supported architectures**: ([more info](https://github.com/docker-library/official-images#architectures-other-than-amd64)) [`amd64`](https://hub.docker.com/r/amd64/nginx/), [`arm32v5`](https://hub.docker.com/r/arm32v5/nginx/), [`arm32v6`](https://hub.docker.com/r/arm32v6/nginx/), [`arm32v7`](https://hub.docker.com/r/arm32v7/nginx/), [`arm64v8`](https://hub.docker.com/r/arm64v8/nginx/), [`i386`](https://hub.docker.com/r/i386/nginx/), [`mips64le`](https://hub.docker.com/r/mips64le/nginx/), [`ppc64le`](https://hub.docker.com/r/ppc64le/nginx/), [`riscv64`](https://hub.docker.com/r/riscv64/nginx/), [`s390x`](https://hub.docker.com/r/s390x/nginx/) - **Published image artifact details**: [repo-info repo's `repos/nginx/` directory](https://github.com/docker-library/repo-info/blob/master/repos/nginx) ([history](https://github.com/docker-library/repo-info/commits/master/repos/nginx)) (image metadata, transfer size, etc) - **Image updates**: [official-images repo's `library/nginx` label](https://github.com/docker-library/official-images/issues?q=label%3Alibrary%2Fnginx) [official-images repo's `library/nginx` file](https://github.com/docker-library/official-images/blob/master/library/nginx) ([history](https://github.com/docker-library/official-images/commits/master/library/nginx)) - **Source of this description**: [docs repo's `nginx/` directory](https://github.com/docker-library/docs/tree/master/nginx) ([history](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 balancer, 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. > [wikipedia.org/wiki/Nginx](https://en.wikipedia.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 arm32v5/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): ```dockerfile FROM arm32v5/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 arm32v5/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](http://nginx.org/en/docs/) (specifically the [Beginner's Guide](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 arm32v5/nginx ``` ### Build a new image with your configuration file ```dockerfile FROM arm32v5/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 arm32v5/nginx configuration (new in 1.19) Out-of-the-box, arm32v5/nginx doesn't support environment variables inside most configuration blocks. But this image has a function, which will extract environment variables before arm32v5/nginx starts. Here is an example using `compose.yaml`: ```yaml web: image: arm32v5/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. - `NGINX_ENVSUBST_TEMPLATE_SUFFIX` - A suffix of template files (default: `.template`) - This function only processes the files whose name ends with this suffix. - `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.template` will be output with the filename `/etc/nginx/conf.d/default.conf`. - This directory must be writable by the user running a container. ## Running arm32v5/nginx in read-only mode To run arm32v5/nginx in read-only mode, you will need to mount a Docker volume to every location where arm32v5/nginx writes information. The default arm32v5/nginx configuration requires write access to `/var/cache/nginx` and `/var/run`. This can be easily accomplished by running arm32v5/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 arm32v5/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 arm32v5/nginx nginx-debug -g 'daemon off;' ``` Similar configuration in `compose.yaml` may look like this: ```yaml web: image: arm32v5/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 arm32v5/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 arm32v5/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 arm32v5/nginx configuration to use directories writeable by that specific UID/GID pair: ```console $ docker run -d -v $PWD/nginx.conf:/etc/nginx/nginx.conf arm32v5/nginx ``` where nginx.conf in the current directory should have the following directives re-defined: ```nginx pid /tmp/nginx.pid; ``` And in the http context: ```nginx http { 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 [Docker NGINX unprivileged image](https://hub.docker.com/r/nginxinc/nginx-unprivileged). # Image Variants The `arm32v5/nginx` images come in many flavors, each designed for a specific use case. ## `arm32v5/nginx:` 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 [Debian](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. ## `arm32v5/nginx:-perl` / `arm32v5/nginx:-alpine-perl` Starting with arm32v5/nginx:1.13.0 / mainline and arm32v5/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. # License View [license information](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 [the `repo-info` repository's `nginx/` directory](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.