add os-release files to images#62
Conversation
Signed-off-by: Bob Callaway <bcallaway@google.com>
discordianfish
left a comment
There was a problem hiding this comment.
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 <bcallaway@google.com>
|
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-exporterin 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