docker-nginx-unprivileged: 1.19.5 regression

The 1.19.5 release just made seems to have broken the entrypoint:

$ docker run -it --rm nginxinc/nginx-unprivileged:1.19.5
Unable to find image 'nginxinc/nginx-unprivileged:1.19.5' locally
1.19.5: Pulling from nginxinc/nginx-unprivileged
Digest: sha256:ed0c9fcace3f7fe25542d5e472fe6d853f3523a6d3362849653cf262ce5ff02a
Status: Downloaded newer image for nginxinc/nginx-unprivileged:1.19.5
docker: Error response from daemon: OCI runtime create failed: container_linux.go:370: starting container process caused: exec: "/docker-entrypoint.sh": permission denied: unknown.

Caught this because our CI/CD pipelines are only pinned to 1.19

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 11
Comments: 20 (3 by maintainers)

Commits related to this issue

Fix executable permissions See #56 — committed to nginxinc/docker-nginx-unprivileged by alessfg 4 years ago

Most upvoted comments

yep, this is a huge regression, breaking alot of CI/CD in the world most likely

philicious on Dec 3, 2020

I would recommend putting some very simple CI in place to validate the images after the build step but before the push step to the container registry.

Eg. After build:

docker run \
  --rm \
  "nginx:nginx-unprivleged:1.18.0" /bin/bash -c 'echo "build ok"'

If it fails, block the merge request.

stephenmoloney on Dec 3, 2020

Aight, new images should be live now. Can you all check and see if your builds are working?

alessfg on Dec 3, 2020

Hey all! I’m tremendously sorry this happened! I’m pushing a fix right now, should hopefully be solved within the next half hour.

alessfg on Dec 3, 2020

Can I ask why it was pushed to the previous tag versions? Our dockerfile references nginxinc/nginx-unprivileged:1.18-alpine, why was that tag referenced as well as 1.19 as this PR seems intended for 1.19?

There’s some changes across all images (eg, the stopsignal has finally changed to sigquit).

alessfg on Dec 3, 2020