-
Notifications
You must be signed in to change notification settings - Fork 39
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
add os-release files to images #62
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: Bob Callaway <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems reasonable but not feeling strongly either way.
I'm not sure we should do this. This copies in the Debian signature, which misrepresents what out BusyBox image is. |
It's your call of course, but since you're sourcing core components from Debian it made sense to me. Another option is that you could still write a file to |
Yes, adding a custom distroless os-release makes more sense to me. Interestingly I checked the official busybox container, it also does not have an os-release. |
Signed-off-by: Bob Callaway <[email protected]>
friendly ping - any thoughts on this updated PR? |
Build is failing. 🤔 |
https://app.circleci.com/pipelines/github/prometheus/busybox It was failing before for something unrelated. |
It would be helpful for image scanners to have
/etc/os-release
(symlinked to/usr/lib/os-release
) included in these images. Right now when runningprometheus/node-exporter
in my cluster, the background image scanners are constantly complaining on every sweep that the OS source of the container can not be detected.The one file is 267 bytes (plus the symlink) so it does not have a meaningful impact on image size.
fyi @SuperQ @sdurrheimer