This message was deleted.

At every build, every steps of my docker image are built again. Whgen only application code change the building and pushing of layers should be minimal, but rn might gh action atkes north of 6 minutes to complete.

@modern-plastic-10593 which registry are you using? (inline caching isn’t supported everywhere)

I use gcp artifact registry

do you have multiple build targets? e.g., something like “FROM base-image AS build-stage” in your dockerfile?

I do have multiple build stage: preparing base, installing deps, building,

there’s a lot that could be going on here, but i suspect what’s happening in your case is your inline cache doesn’t include information about the intermediate build stages, hence why they’re always getting rebuilt.

would it work if I try caching the local docker directory from GitHub action to GitHub action ?

in theory, yes,

--cache-to type=gha

would do the trick, but unfortunately the image resource doesn’t currently expose all of the `--cache-from`/`--cache-to` functionality. this is something we’re going to be working on soon, and if you’re up for it i can keep you posted if you’re interested in beta testing something like this.

Yes, thanks a lot. However for the time being what would you recommend ? It will be dificult to build and push outside of pulumi, as the registry address is known in the IaC. If I prebuild the image on the runner would the pulumi build afterward use the local image ?

it depends on your setup, but in a past life i used docker’s build-push-action with github actions to publish images, and then i consumed those tags from my pulumi program. not ideal but something like that is a viable workaround.

This is not ideal as again the registry itself depends on the IaC and won't be known before it runs. Do you know I could confirm that artifact registry is the source of my caching problems ?