flake-parts VS official-images

There are attempts like

https://flake.parts/

or

https://github.com/nix-community/flakelight

Their aim is to create an ecosystem of reusable Nix libraries. But it is tiny.

You can also just install flakes doing nix profile install . I wrote a tool to make it a bit easier, npt but it's completely optional. Once you install the packages with nix profile. Then in your repos you can use a flake with a devShell and run nix develop. Check https://flake.parts to write your flakes.

Definitely use flakes from the get-go. It's much more sane. Nix's documentation can be unorganized, but read through it when you can. Modules and other projects tend to have their own documentation as well, like Home Manager and flake-parts

That's not a typo, there OP is referring to https://github.com/hercules-ci/flake-parts

Ubuntu now has snapshot.ubuntu.com, see https://ubuntu.com/blog/ubuntu-snapshots-on-azure-ensuring-p...

Related discussion about reproducible builds by the Docker people: https://github.com/docker-library/official-images/issues/160...

> In their updated policy, it appears they now won't remove any existing images, but projects who don't pay up will not be able to publish any new images

This is not correct. It's the "organization" features are going away. That is the feature which lets you create teams, add other users to those teams, and grant teams access to push images and access private repositories. Multiple maintainers can still collaborate on publishing new images through use of access tokens which grant access to publish those images. It's kind of a hack, but it works. You would typically use these access tokens with automated CI tools anyway. This will require converting the organization account to a personal user (non-org) account. (Interesting note/disclosure: I was the engineer who first implemented the feature of converting a personal user account into an organization account some time around 2014/2015, but I no longer work there.)

For open source projects which are not part of the Docker Official Images (the "library" images [1]), they announced that such projects can apply to the Docker-Sponsored Open Source Program [2].

I would also heed the warning from the author of this article:

> Self-hosting a registry is not free, and it's more work than it sounds: it's a proper piece of infrastructure, and comes with all the obligations that implies, from monitoring to promptly applying security updates to load & disk-space management. Nobody (let alone tiny projects like these) wants this job.

Having most container images hosted by a handful of centralized registries has its problems, as noted, but so does an alternative scenario where multiple projects which decided to go self-hosted eventually lack the resources to continue doing so for their legacy users. Though, I suppose the nice thing about container images is that you can always pull and push them somewhere else to keep around indefinitely.

[1] https://hub.docker.com/u/library

Indeed. While I do maintain two of them, that maintenance is effectively equivalent to being an open source maintainer or open source contributor. I do not have any non-public knowledge about the Docker Official Images program. My interaction with the Docker Official Images program can be summed up as “my PRs to docker-library/official-images” (https://github.com/docker-library/official-images/pulls/TimW...) and the #docker-library IRC channel on Libera.Chat.

"AdoptOpenJDK up until now was producing OpenJDK binaries with both Hotspot and OpenJ9 VM's. With Adopt's move to Eclipse, legal restrictions prevent the new Eclipse Adoptium group from producing/releasing OpenJ9 based binaries. As a result, IBM will be producing OpenJ9 based binaries in 2 flavours, Open and Certified, both under the family name IBM Semeru Runtimes. Essentially the same binaries, released under different licenses."

Source: https://github.com/docker-library/official-images/pull/10666...

They should be available soon, the corresponding PR at docker-library/official-images has already been merged: https://github.com/docker-library/official-images/pull/13693

Official image lists are added here: https://github.com/docker-library/official-images/tree/master/library

Looks like this PR will release the official version to the hub: https://github.com/docker-library/official-images/pull/12382

We’ve also officially release containers for ppc64le available on all the major registries and we’ve also gone ahead and updated our containers to 8.5.4 and patched against the latest security updates where applicable. 18 packages have been updated and you can see that work here.