-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The dockerfile installs dumb-init but doesn't use it #9858
Comments
This issue is currently awaiting triage. If Ingress contributors determines this is a relevant issue, they will accept it by applying the The 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. |
/remove-kind bug
|
Hello, The impact is that its an unnecessary package which could trigger findings in users vulnerability scans if a CVE is found in the package. This is a similar problem to one discussed and fixed in an issue opened against the nginx upstream docker image because curl is included in the nginx image itself, so I request you to review the additional discussion which is available in that issue around this type of issue.
I just did a quick github search in this project and did not find any reference to it in the code. I am not currently a user but was evaluating the project and investigating how the container is built for a possible POC, and this caught my eye. |
Making use of dumb-init would support #8034 |
@tspearconquest comment on the existence of this line ingress-nginx/rootfs/Dockerfile Line 85 in 4e8d0b5
based on the above line, it looks as if your claim is false, if/when you say/mean |
Hello,
The file I'm referring to is under the images/rootfs directory, not the rootfs directory in the repo root: https://github.com/kubernetes/ingress-nginx/blob/4e8d0b5836096426393340273260b9000cd1e151/images/nginx/rootfs/Dockerfile
Please check it and advise
Get Outlook for Android<https://aka.ms/AAb9ysg>
…________________________________
From: Long Wu Yuan ***@***.***>
Sent: Thursday, April 13, 2023 9:39:51 PM
To: kubernetes/ingress-nginx ***@***.***>
Cc: Thomas Spear ***@***.***>; Mention ***@***.***>
Subject: Re: [kubernetes/ingress-nginx] The dockerfile installs dumb-init but doesn't use it (Issue #9858)
CAUTION: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
@tspearconquest<https://github.com/tspearconquest> comment on the existence of this line https://github.com/kubernetes/ingress-nginx/blob/4e8d0b5836096426393340273260b9000cd1e151/rootfs/Dockerfile#L85
based on the above line, it looks as if your claim is false, if/when you say/mean "dumb-init" is not being used .
If you meant to say something else, its not clear as to what problem needs to be solved.
—
Reply to this email directly, view it on GitHub<#9858 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ATRTFZ2CGKDTF2KB4YILJ2TXBC2HPANCNFSM6AAAAAAW5UVG2Q>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Thanks for clarifying that. Please inspect code to know more. There is a
base image and then there is a controller image.
/close
…On Fri, 14 Apr, 2023, 8:15 am tspearconquest, ***@***.***> wrote:
Hello,
The file I'm referring to is under the images/rootfs directory, not the
rootfs directory in the repo root:
https://github.com/kubernetes/ingress-nginx/blob/4e8d0b5836096426393340273260b9000cd1e151/images/nginx/rootfs/Dockerfile
Please check it and advise
Get Outlook for Android<https://aka.ms/AAb9ysg>
________________________________
From: Long Wu Yuan ***@***.***>
Sent: Thursday, April 13, 2023 9:39:51 PM
To: kubernetes/ingress-nginx ***@***.***>
Cc: Thomas Spear ***@***.***>; Mention ***@***.***>
Subject: Re: [kubernetes/ingress-nginx] The dockerfile installs dumb-init
but doesn't use it (Issue #9858)
CAUTION: This email originated from outside the organization. Do not click
links or open attachments unless you recognize the sender and know the
content is safe.
@tspearconquest<https://github.com/tspearconquest> comment on the
existence of this line
https://github.com/kubernetes/ingress-nginx/blob/4e8d0b5836096426393340273260b9000cd1e151/rootfs/Dockerfile#L85
based on the above line, it looks as if your claim is false, if/when you
say/mean "dumb-init" is not being used .
If you meant to say something else, its not clear as to what problem needs
to be solved.
—
Reply to this email directly, view it on GitHub<
#9858 (comment)>,
or unsubscribe<
https://github.com/notifications/unsubscribe-auth/ATRTFZ2CGKDTF2KB4YILJ2TXBC2HPANCNFSM6AAAAAAW5UVG2Q
>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
—
Reply to this email directly, view it on GitHub
<#9858 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABGZVWRUS2ZNIPHNEBOIW5TXBC247ANCNFSM6AAAAAAW5UVG2Q>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
@longwuyuan: Closing this issue. In response to this:
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. |
What happened:
I noticed the dockerfile installs
dumb-init
but doesn't make use of it.What you expected to happen:
I expected nginx to use dumb-init in the entrypoint, or not install it.
NGINX Ingress controller version (exec into the pod and run nginx-ingress-controller --version.): Look in the master branch (all versions)
Kubernetes version (use
kubectl version
):Doesn't matter, but for posterity:
Environment:
Cloud provider or hardware configuration: AKS K8s 1.24 on various node sizes
OS (e.g. from /etc/os-release): Ubuntu 18.04
Kernel (e.g.
uname -a
): 5.4.0-1103-azure_109How was the ingress-nginx-controller installed: It wasn't, I noticed this while reviewing the dockerfile code
Current State of the controller: N/A
Current state of ingress object, if applicable: N/A
Others:
How to reproduce this issue:
Look at the dockerfile
Anything else we need to know:
Really, look at the dockerfile.
The text was updated successfully, but these errors were encountered: