[NGINX] New image tagged 1.27.0 caused startup failure
Platform
AWS
bndiagnostic ID know more about bndiagnostic ID
n/a
bndiagnostic output
No response
bndiagnostic was not useful. Could you please tell us why?
Issue occurring in hosted EKS env
Describe your issue as much as you can
We switched to bitnami/nginx 1.27.0 a couple weeks ago and everything was working great. We pull the image from the public AWS ECR.
Everything was working great until there was a new version pushed this morning with the same tag as what we were using: 1.27.0.
With this version on startup we are getting:
nginx: [emerg] mkdir() "/opt/bitnami/nginx/client_body_temp" failed (13: Permission denied)
Our k8s pods that run that container get stuck into a crash loop. Wondering two things:
- What might be causing this?
- Why was a new version published under the same tag as something that already existed?
Hi @tj-wd,
Thanks for using Bitnami. 1.27.0 is a rolling tag and it will get updated with any new release. If you need to pin to a previous version, you can use the next one:
bitnami/nginx:1.27.0-debian-12-r5
You can check other tags at https://hub.docker.com/r/bitnami/nginx/tags/
Hi @tj-wd,
Thanks for using Bitnami.
1.27.0is a rolling tag and it will get updated with any new release. If you need to pin to a previous version, you can use the next one:bitnami/nginx:1.27.0-debian-12-r5You can check other tags at https://hub.docker.com/r/bitnami/nginx/tags/
Thanks @gongomgra . I guess that makes sense that it is done to stay in sync with the official nginx versions.
Any idea what changed in the most recent version that could cause the issue we saw?
@tj-wd I don't see any important change in 1.27.0 revisions in our GitHub history, but you can inspect them at https://github.com/bitnami/containers/commits/main/bitnami/nginx. You can compare all changes against the specific revision you were using before from there.
Thanks for sharing Receiptify com
@tj-wd I don't see any important change in 1.27.0 revisions in our GitHub history, but you can inspect them at https://github.com/bitnami/containers/commits/main/bitnami/nginx. You can compare all changes against the specific revision you were using before from there.
So the only change between r5 and r6 is essentially a version number change? Or am I looking at this wrong
Hi currently experiencing this same issue, the new image seems to be breaking lots of our service.
Hi @tj-wd and @danielbarr3ra,
I have checked this with the engineering team and this issue seems to be located on our side. We are working on a fix for this.
Hi @tj-wd @danielbarr3ra,
We released a new revision of our NGINX container updating the /opt/bitnami/nginx default permission that should fix the reported issue:
$ docker-compose up -d && docker-compose logs -f
[+] Running 2/2
✔ nginx Pulled 20.6s
✔ 7018e03dc919 Pull complete 15.2s
[+] Running 2/2
✔ Network nginx_default Created 0.1s
✔ Container nginx-nginx-1 Started
$ docker-compose exec -it nginx bash
I have no name!@b2cf9c69738e:/app$ touch /opt/bitnami/nginx/test.txt
I have no name!@b2cf9c69738e:/app$ ls -larth /opt/bitnami/nginx
total 12K
drwxr-xr-x 1 root root 10 Aug 21 18:46 sbin
drwxr-xr-x 1 root root 232 Aug 21 18:46 modules
drwxr-xr-x 1 root root 314 Aug 21 18:46 licenses
-rw-r--r-- 1 root root 7.0K Aug 21 19:24 .spdx-nginx.spdx
drwxr-xr-x 1 root root 10 Aug 23 14:53 ..
drwxrwxr-x 1 root root 38 Aug 23 14:54 logs
lrwxrwxrwx 1 root root 4 Aug 23 14:54 html -> /app
drwxrwxr-x 1 root root 454 Aug 23 14:54 conf.default
drwxrwxr-x 1 root root 20 Aug 23 14:54 conf
drwxrwxr-x 1 root root 82 Aug 26 07:40 tmp
-rw-r--r-- 1 1001 root 0 Aug 26 07:41 test.txt
drwxrwxr-x 1 root root 30 Aug 26 07:41 .
You can get more details on the changes included in the new image from its associated pull request at https://github.com/bitnami/containers/pull/71178
Hope it helps!
Checking :)
Hi @danielbarr3ra, Have you found any issue? If everything is OK I will proceed to close the issue
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.