Build nginx image with FromAsCasing

[haojingcn]

What happened: In nginx image build, run make build, occur the error with FromAsCasing.

What you expected to happen: No Error; Not interrupted.

NGINX Ingress controller version (exec into the pod and run nginx-ingress-controller --version.): In branch main. commitId 3c4e78e6b755eb33821c4477106f424bd8792d8f. I think it very new.

Kubernetes version (use kubectl version): Irrelevant It's build error, so not with Kubernetes version.

Environment:

• Cloud provider or hardware configuration: Intel(R) Xeon(R) CPU E5-2650 v3 @ 2.30GHz

• OS (e.g. from /etc/os-release): Debian GNU/Linux 10 (buster)

• Kernel (e.g. uname -a): 4.19.0-24-amd64 #1 SMP Debian 4.19.282-1 (2023-04-29) x86_64 GNU/Linux

• Install tools: docker, make

  • make: ii make 4.2.1-1.2 amd64 utility for directing compilation
  • docker: ii docker-ce 5:20.10.17~3-0~debian-buster amd64 Docker: the open-source application container engine

• Basic cluster related info: Irrelevant

• How was the ingress-nginx-controller installed: Irrelevant

• Current State of the controller: Irrelevant

• Current state of ingress object, if applicable: Irrelevant

• Others: No

How to reproduce this issue: cd images; make build

Anything else we need to know: No

[k8s-ci-robot]

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

[haojingcn]

I supposed it caused by https://docs.docker.com/reference/build-checks/from-as-casing/

[longwuyuan]

/remove-kind bug /kind support /triage needs-information

The information you have provided is very difficult to use to make comments.

• Try to answer the questions that are asked in the template of a new bug report. It will provide context
• Try to copy/paste the commands you executed and the complete outputs of those commands. Screenshots are almost always useless and very hard to use to make helpful comments, in such issues

You can also just fork the project, then clone to your laptop, and making sure that you have the required tools like kind make docker etc etc, youcan try to run `make dev-env" as explained here https://kubernetes.github.io/ingress-nginx/developer-guide/getting-started/#local-build

[longwuyuan]

Since you have not responded, I will close this for now. Feel free to reopen after you have provided more detailed information.

/close

[k8s-ci-robot]

@longwuyuan: Closing this issue.

In response to [this](https://github.com/kubernetes/ingress-nginx/issues/11506#issuecomment-2201659626): >Since you have not responded, I will close this for now. Feel free to reopen after you have provided more detailed information. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.