No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

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.

<@U0695PG51FY> which registry are you using? (inline caching isn’t supported <https://github.com/aws/containers-roadmap/issues/876|everywhere>)

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,

If it ever comes to that, would it work if I try caching the local docker directory from GitHub action to GitHub action ?

With the cache from props, pulumi downloads my previous image but does not seem to find cached steps from there

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.

&gt; 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 ?

Or is there a way to push an image built outside, upstream from pulumi ?

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 ?

&gt; here’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.
Alternatively, would moving out of a multistage build augment my chances of using a cache ? I do not care about how the dockerfile is set up, i only wish to decrease my time to deploy. Now sitting around 6 minutes, it's not an ideal feedback loop.

And finally, maybe I am missing somehting in my action definition ? For instance, do I need to manually setup anything on top of the pulumi deploy action (docker buildx or other tools ?)

I guess the `registry`type backend is not supported bu the docker Image pulumi component