Repository navigation
taskgraph load-task should cache docker images #788
Description
Currently, if you run, say taskgraph load-task Ww-q-IvVTfed8xepUhNWaw twice, you'll see:
2025-09-26 15:54:49,487 - INFO - Downloading from https://community-tc.services.mozilla.com/api/queue/v1/task/MUvi2npBRue4VmksTmsdEw/artifacts/public/image.tar.zst
Loaded image: ci:latesteach time in the logs. It would be useful to cache this downloaded image, as some of these images are large and this takes up a good portion of the time when running load-task.
Subsequent runs would be much faster and help the local debugging/development process.
Activity
[-]`taskgraph load-task` should cache downloaded artifact images[/-][+]`taskgraph load-task` should cache docker images[/+]matt-boris commentedon Dec 22, 2025
Another instance would be making changes to an in-tree Dockerfile and testing against multiple different taskIDs. Each run of
taskgraph load-task --image <in-tree image name> <taskID>rebuilds the same image.ahal commentedon Dec 22, 2025
Implementation note:
We probably need to extract the digest hashes that Taskgraph computes as part of the
cached_tasktransforms. Then upon building the image, we apply a tag containing this hash to the image in the local registry. On subsequent calls tobuild_image, we then check whether an image with the same digest tag exists and return that if so.We'll probably also want to add a
--forceflag to force a rebuild even if there's a locally cached option.