Some of the 1.29.0 version Dockerfiles lacking version ENV variable and return 1.28.0 when checked.

[FairyPenguin]

Bug Overview

Evening,

hope you are doing well and thanks for the effort.

When i started using the 1.29.0 version Docker-Images today i noticed some of them does return
nginx version: nginx/1.28.0 when using the command nginx -v to check and verify version.

So i checked the docker-files and found, YES the files are lacking the ENV variable for nginx version
which is ENV NGINX_VERSION 1.29.0

Here for example:

https://github.com/nginx/docker-nginx/blob/7895505c41013f66d3841cd2613b436229c1fe0e/mainline/alpine/Dockerfile

But here the ENV variable for nginx version is there

https://github.com/nginx/docker-nginx/blob/7895505c41013f66d3841cd2613b436229c1fe0e/mainline/debian/Dockerfile

The hash for image i tested
sha256:b2e814d28359e77bd0aa5fed1939620075e4ffa0eb20423cc557b375bd5c14ad
from here
https://hub.docker.com/layers/library/nginx/1.29.0-alpine3.22/images/sha256-2598e977ffd4c4cac6fe01ccab90e30186baa34ccea11a2f0e71938571f19da1

Expected Behavior

The 1.29.0 docker-images should return nginx version: nginx/1.29.0 but they return nginx version: nginx/1.28.0

Steps to Reproduce the Bug

1- I used the docker-images for the new version 1.29.0 from here:

https://hub.docker.com/_/nginx/tags?name=1.29.0

2- Did a version check with nginx -v

Environment Details

• Version/release of Docker and method of installation (e.g. Docker Desktop / Docker Server)
  1.29.0 Docker on a VPS with Docker compose.
• Version of the Docker NGINX image or specific commit: [e.g. 1.4.3/commit hash]
  Hash: sha256:b2e814d28359e77bd0aa5fed1939620075e4ffa0eb20423cc557b375bd5c14ad
• Target deployment platform: [e.g. OpenShift/Kubernetes/Docker Compose/local cluster/etc...]
  Docker-Swarm and Docker-Compose
• Target OS: [e.g. RHEL 9/Ubuntu 24.04/etc...]
  Ubuntu 24.04.2 LTS (GNU/Linux 6.8.0-62-generic x86_64)

Additional Context

I don't know if this is normal behavior or it's a bug.

[thresheek]

Hi @FairyPenguin

Can you point to an exact image exhibiting this issue?

Cause I'm getting the correct output:

$ docker run -ti --rm nginx@sha256:b2e814d28359e77bd0aa5fed1939620075e4ffa0eb20423cc557b375bd5c14ad nginx -v | grep ^nginx
nginx version: nginx/1.29.0

$ docker run -ti --rm nginx@sha256:b2e814d28359e77bd0aa5fed1939620075e4ffa0eb20423cc557b375bd5c14ad env | grep -i version
NGINX_VERSION=1.29.0
NJS_VERSION=0.9.0

[thresheek]

I've checked arm64, amd64 and i386 platforms, for what it's worth - and it seems to be correct over there.

[FairyPenguin]

@thresheek

Thanks very much, I'm really sorry it was my mistake.

It's the first time i face something like this,

I pulled the right docker image with the right hash for version 1.29.0 and everything was Okay and correct and should continue like this, except i had an error in my nginx.conf

nginx: [emerg] unknown directive "more_clear_headers" in /etc/nginx/nginx.conf:153

And because I was using Docker-Swarm with rollback_config: option, it didn't deploy the update with the error and kept the old container running with version 1.28.0, Even the pipeline was showing zero errors or problems and the deployment runs smoothly.

I didn't catch it until I ran the same Image (Which I built on the 1.29.0) locally with the command

docker run -ti --rm --- And here it returned the error.

Again, Sorry for any disturbance or problems I caused and thanks for your immediate help.

[thresheek]

No worries!