[ECR] [request]: Support for Docker Hardened Images on Enhanced Vulnerability Scanning - Inspector

[janiworldline]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Tell us about your request
I want us AWS Inspector Vulnerability Scans with for Docker Hardened Images

Which service(s) is this request for?
ECR

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
I have built my docker images based on docker hardened images. To be more specific, this one:

dhi.io/amazoncorretto:21-alpine3.22

But when uploading this to the ECR I see this nice little image:

It would be very nice to be able to scan images from dhi.io

Are you currently working around this issue?
Yes, we are using Trivy, even though it is not the official tool we use for container scanning. Would be a lot better to use Inspector

Additional context
I could not find any other issue for this, which surprised me a bit.

[janiworldline]

Also, just to make this proper, we are using the dhi.io/alpine-base:3.22 image as well.

[aomayden]

Same issue here, but with the dhi.io/python:3.13-alpine3.23 image

[bennos3]

Work-around for those interested.
You can set the NAME value in /etc/os-release to the one which AWS Inspector does recognise.

eg.
from NAME="Docker Hardened Images (Alpine)" to NAME="Alpine Linux"
for Alpine based images:

RUN sed -i 's/^NAME=.*/NAME="Alpine Linux"/' /etc/os-release && \
  grep VERSION_ID /etc/os-release | cut -d= -f2 > /etc/alpine-release