update README.md
This commit is contained in:
40
README.md
40
README.md
@@ -1,33 +1,39 @@
|
||||

|
||||
|
||||
# NGINX
|
||||
[<img src="https://img.shields.io/badge/github-source-blue?logo=github&color=040308">](https://github.com/11notes/docker-NGINX)[<img src="https://img.shields.io/github/issues/11notes/docker-NGINX?color=7842f5">](https://github.com/11notes/docker-NGINX/issues)
|
||||
[<img src="https://img.shields.io/github/issues/11notes/docker-NGINX?color=7842f5">](https://github.com/11notes/docker-NGINX/issues)
|
||||
|
||||
Nginx, slim and distroless to be used behind a reverse proxy or as full version
|
||||
Nginx, slim and distroless to be used behind a reverse proxy or as full version as a proxy
|
||||
|
||||
# INTRODUCTION 📢
|
||||
|
||||
nginx (engine x) is an HTTP web server, reverse proxy, content cache, load balancer, TCP/UDP proxy server, and mail proxy server.
|
||||
|
||||
# SYNOPSIS 📖
|
||||
**What can I do with this?** This image will serve as a base for nginx related images that need a high-performance webserver. The default tag of this image is stripped for most functions that can be used by a reverse proxy in front of nginx, it adds however important webserver functions like brotli compression. The default tag is not meant to run as a reverse proxy, use the full image for that. The default tag does not support HTTPS for instance!
|
||||
**What can I do with this?** This image will serve as a base for nginx related images that need a high-performance webserver. The default tag of this image is stripped for most functions that can be used by a reverse proxy in front of nginx, it adds however important webserver functions like brotli compression. The default tag is not meant to run as a reverse proxy, use the full image for that. **The default tag does not support HTTPS for instance!**
|
||||
|
||||
# UNIQUE VALUE PROPOSITION 💶
|
||||
**Why should I run this image and not the other image(s) that already exist?** Good question! All the other images on the market that do exactly the same don’t do or offer these options:
|
||||
**Why should I run this image and not the other image(s) that already exist?** Good question! Because ...
|
||||
|
||||
> [!IMPORTANT]
|
||||
>* This image runs as 1000:1000 by default, most other images run everything as root
|
||||
>* This image has no shell since it is 100% distroless, most other images run on a distro like Debian or Alpine with full shell access (security)
|
||||
>* This image does not ship with any critical or high rated CVE and is automatically maintained via CI/CD, most other images mostly have no CVE scanning or code quality tools in place
|
||||
>* This image is created via a secure, pinned CI/CD process and immune to upstream attacks, most other images have upstream dependencies that can be exploited
|
||||
>* This image contains a proper health check that verifies the app is actually working, most other images have either no health check or only check if a port is open or ping works
|
||||
>* This image works as read-only, most other images need to write files to the image filesystem
|
||||
>* This image is a lot smaller than most other images
|
||||
>* ... this image runs [rootless](https://github.com/11notes/RTFM/blob/main/linux/container/image/rootless.md) as 1000:1000
|
||||
>* ... this image has no shell since it is [distroless](https://github.com/11notes/RTFM/blob/main/linux/container/image/distroless.md)
|
||||
>* ... this image is auto updated to the latest version via CI/CD
|
||||
>* ... this image has a health check
|
||||
>* ... this image runs read-only
|
||||
>* ... this image is automatically scanned for CVEs before and after publishing
|
||||
>* ... this image is created via a secure and pinned CI/CD process
|
||||
>* ... this image verifies external payloads if possible
|
||||
>* ... this image is very small
|
||||
|
||||
If you value security, simplicity and the ability to interact with the maintainer and developer of an image. Using my images is a great start in that direction.
|
||||
If you value security, simplicity and optimizations to the extreme, then this image might be for you.
|
||||
|
||||
# COMPARISON 🏁
|
||||
Below you find a comparison between this image and the most used or original one.
|
||||
|
||||
| **image** | 11notes/nginx:1.28.0 | nginx:1.28.0-alpine-slim |
|
||||
| **image** | 11notes/nginx:1.28.0 | nginx:1.28.0 |
|
||||
| ---: | :---: | :---: |
|
||||
| **image size on disk** | 4.41MB | 11.9MB |
|
||||
| **image size on disk** | 3.69MB | 192MB |
|
||||
| **process UID/GID** | 1000/1000 | 0/0 |
|
||||
| **distroless?** | ✅ | ❌ |
|
||||
| **rootless?** | ✅ | ❌ |
|
||||
@@ -168,7 +174,7 @@ These are the main tags for the image. There is also a tag for each commit and i
|
||||
* [stable](https://hub.docker.com/r/11notes/nginx/tags?name=stable)
|
||||
|
||||
### There is no latest tag, what am I supposed to do about updates?
|
||||
It is of my opinion that the ```:latest``` tag is super dangerous. Many times, I’ve introduced **breaking** changes to my images. This would have messed up everything for some people. If you don’t want to change the tag to the latest [semver](https://semver.org/), simply use the short versions of [semver](https://semver.org/). Instead of using ```:1.28.0``` you can use ```:1``` or ```:1.28```. Since on each new version these tags are updated to the latest version of the software, using them is identical to using ```:latest``` but at least fixed to a major or minor version.
|
||||
It is of my opinion that the ```:latest``` tag is dangerous. Many times, I’ve introduced **breaking** changes to my images. This would have messed up everything for some people. If you don’t want to change the tag to the latest [semver](https://semver.org/), simply use the short versions of [semver](https://semver.org/). Instead of using ```:1.28.0``` you can use ```:1``` or ```:1.28```. Since on each new version these tags are updated to the latest version of the software, using them is identical to using ```:latest``` but at least fixed to a major or minor version.
|
||||
|
||||
If you still insist on having the bleeding edge release of this app, simply use the ```:rolling``` tag, but be warned! You will get the latest version of the app instantly, regardless of breaking changes or security issues or what so ever. You do this at your own risk!
|
||||
|
||||
@@ -187,7 +193,7 @@ docker pull quay.io/11notes/nginx:1.28.0
|
||||
>This image is not based on another image but uses [scratch](https://hub.docker.com/_/scratch) as the starting layer.
|
||||
>The image consists of the following distroless layers that were added:
|
||||
>* [11notes/distroless](https://github.com/11notes/docker-distroless/blob/master/arch.dockerfile) - contains users, timezones and Root CA certificates
|
||||
>* [11notes/distroless:curl](https://github.com/11notes/docker-distroless/blob/master/curl.dockerfile) - app to execute HTTP or UNIX requests
|
||||
>* [11notes/distroless:curl](https://github.com/11notes/docker-distroless/blob/master/curl.dockerfile) - app to execute HTTP requests
|
||||
|
||||
# BUILT WITH 🧰
|
||||
* [nginx](https://nginx.org)
|
||||
@@ -200,4 +206,4 @@ docker pull quay.io/11notes/nginx:1.28.0
|
||||
# ElevenNotes™️
|
||||
This image is provided to you at your own risk. Always make backups before updating an image to a different version. Check the [releases](https://github.com/11notes/docker-nginx/releases) for breaking changes. If you have any problems with using this image simply raise an [issue](https://github.com/11notes/docker-nginx/issues), thanks. If you have a question or inputs please create a new [discussion](https://github.com/11notes/docker-nginx/discussions) instead of an issue. You can find all my other repositories on [github](https://github.com/11notes?tab=repositories).
|
||||
|
||||
*created 04.06.2025, 21:56:22 (CET)*
|
||||
*created 03.08.2025, 03:35:59 (CET)*
|
Reference in New Issue
Block a user