yosifkit

> Relevant to the CI failure, I would love to check back in on [#12399 (comment)](https://github.com/docker-library/official-images/pull/12399#issuecomment-1123014876) -- any update on removing or updating those older versions? grimacing Friendly ping. Any...

We recommend against using blanket package upgrades (`apt-get upgrade`/`apk upgrade`/`yum upgrade`/`yum update`) for official-images. When package upgrades are applied in a dependent image, it duplicates content of the base image,...

Friendly ping. Any update regarding the [`dnf -y update`](https://github.com/docker-library/official-images/pull/13081#issuecomment-1320410250)?

It's not a hard requirement for the Dockerfiles to be in a separate repo, but a quick warning about putting the Dockerfile in the root of the upstream repo: https://github.com/docker-library/official-images/pull/11100#issuecomment-1023481834....

Unfortunately, since we don't have any configuration points to just build a single target within a multistage build, I think that Dockerfile would fail to build for us (since our...

The information above is still correct and answers the questions about being `FROM` an image outside of Docker Official Images and about hosting the Dockerfile in the upstream code repo....

> > if FROM scratch, tarballs only exist in a single commit within the associated history? > > What kind of history is needed? No force pushes I guess? Most...

In hindsight the `POSTGRES_USER` env was a poor choice of name. At this point, I think that we would break too many users by changing what access the `POSTGRES_USER` has...

Using your suggestion, it is not that hard to extend the image for your own needs. Unfortunately, I don't think this is something we want to add to the image...

It looks like someone is currently working on adding git credentials support: https://github.com/go-git/go-git/issues/490. So, we should wait until that is available. (also, we shouldn't be pulling in any dependencies from...