Hacker News Reader

> Do you have particular scenarios you’d like the Dockerfiles for or is it just for transparency/ trust (which is a totally valid reason of course)?

The latter. You or an attacker could tamper with the images - however even with the Dockerfiles I can't be sure that the provided images are built from the Dockerfiles, so in the end I'd have to trust you anyway. Also I'd be curious how you build the images.

Thanks for your answer!

View on HN

Totally get it… practically if you don’t want to have to deal with constantly updating images you have to have some degree of trust in whomever you get them from… that said, we try to be as transparent as possible with a cryptographically verifiable SBOM for every build of every image, signing every image, providing detailed compliance test results for FIPS, STIG, CIS (see the compliance tab on each image listing)

Your feedback about Dockerfiles is good though and probably something we can easily add to image listings. I opened an issue for us to add.

Note that we also make our package manager freely available in Community Edition as well, which can make the Dockerfile availability more useful.

Would be nice to see logs from the CI runs building the images, to see the hashes of inputs and outputs. Useful, I guess unless the logs were tampered with also.

Reply on news.ycombinator.com