Update nginx base image in one place

[strongjz]

Signed-off-by: James Strong strong.james.e@gmail.com

Forcing nginx base image to be updated in one place.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation only

[longwuyuan]

% docker run -it 814814d45cfa sh
docker: Error response from daemon: failed to create shim: OCI runtime create failed: container_linux.go:380: starting container process caused: exec: "/usr/local/entrypoint.sh": permission denied: unknown.
[~]

The tests for this will never pass.
We need to build & promote the base image again and see if that will make the tests pass.
@theunrealgeek did some debugging and discovered that a recent PR related to OpenTelemetry introduced a /images/nginx/rootfs/entrypoint.sh script in the base nginx image. But this script does not have execute permission and hence the containers based on the base nginx image we promoted recently, will never start. Thus any pod based on those containers will never go into running state and that is why we observe a crashloopbackoff in the e2etest pod during the tests.

pod/slow-echo-7788879c45-j62t2                 0/1     CrashLoopBackOff   4          91s

The e2etest slow-echo pod images also uses the nginx base image that we have pushed couple of days ago and that does not have the execute bit set on the script entrypoint.sh.

% docker pull k8s.gcr.io/ingress-nginx/nginx:9960efe1e9a9c6e944967b52e1a8a7b7b659874d@sha256:99f079bc9e418b450e0902ea78e86c70315dad3a420871d29e812c55cc0beea1
k8s.gcr.io/ingress-nginx/nginx@sha256:99f079bc9e418b450e0902ea78e86c70315dad3a420871d29e812c55cc0beea1: Pulling from ingress-nginx/nginx
36ccefbf3d8a: Already exists 
fd5815e0c0d0: Already exists 
989ebcc4d2f6: Already exists 
44eaefdb6147: Already exists 
95d8b70dffe6: Already exists 
5545eb951fd1: Already exists 
Digest: sha256:99f079bc9e418b450e0902ea78e86c70315dad3a420871d29e812c55cc0beea1
Status: Downloaded newer image for k8s.gcr.io/ingress-nginx/nginx@sha256:99f079bc9e418b450e0902ea78e86c70315dad3a420871d29e812c55cc0beea1
k8s.gcr.io/ingress-nginx/nginx:9960efe1e9a9c6e944967b52e1a8a7b7b659874d@sha256:99f079bc9e418b450e0902ea78e86c70315dad3a420871d29e812c55cc0beea1
[~] 
% docker images
REPOSITORY                                    TAG         IMAGE ID       CREATED          SIZE
ingress-controller/controller                 1.0.0-dev   13f622b0c6f0   11 minutes ago   285MB
nginx-ingress-controller                      e2e         56ac7d8a808c   8 hours ago      191MB
k8s.gcr.io/ingress-nginx/nginx                <none>      814814d45cfa   2 days ago       185MB
gcr.io/k8s-staging-ingress-nginx/controller   1.1.2-dev   bc9817c8dba2   8 days ago       292MB
alpine                                        3.14.4      a33ac4f1069a   13 days ago      5.59MB
kindest/node                                  v1.23.4     6b76f7b7813a   3 weeks ago      1.47GB
k8s.gcr.io/ingress-nginx/e2e-test-runner      <none>      d3e563a814e5   2 months ago     1.15GB
kindest/node                                  <none>      32b8b755dee8   10 months ago    1.12GB
[~] 
% docker run -it 814814d45cfa sh
docker: Error response from daemon: failed to create shim: OCI runtime create failed: container_linux.go:380: starting container process caused: exec: "/usr/local/entrypoint.sh": permission denied: unknown.
[~] 

@strongjz , can we build and promote a new nginx base image, with execute permission set on /images/nginx/rootfs/entrypoint.sh when you come online

[strongjz]

@rikatz @tao12345666333 @longwuyuan Can you all review these changes.

[strongjz]

/label tide/merge-method-squash

[strongjz]

/test pull-ingress-nginx-test

[tao12345666333]

/lgtm

hold for CI
/hold

[strongjz]

/hold cancel
/lgtm

[k8s-ci-robot]

@strongjz: you cannot LGTM your own PR.

In response to this:

/hold cancel
/lgtm

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: strongjz, tao12345666333

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [strongjz,tao12345666333]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment