Daily log: verified tool cache in operator testing
Developer tools can now be installed into containers from a checked cache. For now only the operator account can use it.
Nobody outside the operator account notices anything yet: the verified tool cache is switched off for all other accounts. No action is needed.
The verified tool cache we started on 10 November now works end to end, for now only on the operator account. A separate service fetches developer tools from their official sources, checks each download against the checksum the project publishes, checks the licence, and keeps the result in a cache of up to 1 TB. About 210 of the 300 listed tools have passed so far, among them Node.js, Go, kubectl, ripgrep, yq, ruff and the common database clients.
From a container, a tool installs in seconds without the container needing internet access. The files are checked again inside the container before they are switched on. A daily run picks up new upstream versions, builds and checks them first, and keeps the two previous versions for a quick way back. Containers with auto-update on get the new version within six hours.
Today we tested the whole path on live systems: installs from three different package types, a refused install into a stopped container, and the update run. It is switched off for everyone else. Before it opens up, we will publish a separate post.