Cache docker manifests about bacalhau HOT 1 CLOSED

I want to flag that the description has the potential to clash with #2255 (recent comments in #2255 came from conversation in #2351).

latest and versioned tags

I believe that compute nodes should never encounter a latest tag or an untagged image. As a reference, the Kubernetes documentation advises against using the latest tag. While some users may still want to use it, we can accommodate them by resolving the latest tag to a specific image digest at the Requester level. This ensures that highly concurrent Docker jobs using latest will run the same image. Since tags are (sadly) mutable I would too like to resolve these at the Requester level, however I have less strong feelings on this since its rare for tags to change. (as you have already pointed out)

In an open network with third-party Requester and Compute nodes, the decision to permit the latest tag will depend on their developers. However, in our implementation, we should require the Requester level to resolve the latest tag and prevent any specification with the latest reference from reaching a compute node.

My point here is that I would like to prevent compute nodes from caching (or even seeing!) a latest tag and to instead handle caching of this information via the Requester node(s). And ideally resolve tagged versions in a similar fashion.

image digest

In full agreement that these can be cached by compute nodes.

from bacalhau.