Jon Johnson

I think the wall of SHAs is a pretty decent UX, honestly. You can just pick an arbitrary commit for distroless and easily discover which image corresponds to that commit....

> Why doesn't distroless have releases? That's a great question, and I think the answer is partially cultural and partially technical. Culturally, Google doesn't really have releases internally. Everything just...

> RE: Pinning to releases being "not good"... I disagree. > > As much as I admire the "100% rolling" culture at google, this is not tenable for most organizations....

> All valid points. At this point is seems like the path is set and I'm tilting at windmills, but let me try to respond anyway. I'm not trying to...

@hasheddan I've edited the issue body to fix the `recent change` link, just FYI.

> what do you think about the proposed upstream change to go-containerregistry? That sounds reasonable to me, something like `func ParseHealthConfig(s string) (*HealthConfig, error)`? I'm happy to review a PR.

Somewhat blocked on https://github.com/bazelbuild/bazel/issues/6519 Some discussion in https://github.com/bazelbuild/rules_docker/issues/300 I've got ideas in https://github.com/bazelbuild/rules_docker/issues/1695#issuecomment-748254384 but need some guidance re: the rules UX.

[This doc](https://docs.google.com/document/d/1moQfNcEIttsk6vYanNKIy3ZuK53hQUFq1b1r0rmsYVg/edit) seems relevant for air-gapped environments.

I don't think we document `ko run` anywhere, and maybe we should hide it... it's a bit janky.

> Flag --generator has been deprecated, has no effect and will be removed in the future. hmmm