Image: can we add --pull and --no-cache options?

[jdahlq]

Hello!

• Vote on this issue by adding a 👍 reaction
• If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

docker.Image doesn't have the ability to force a re-pull of the base image. For example, if I have a Dockerfile like this...

FROM cloudflare/cloudflared:latest
CMD ["version]

... then Docker won't pull the newest version of the cloudflare/cloudflared base image if there is one cached locally.

Could we expose the --pull and --no-cache flags as Image arguments? Looks fairly straightforward to plumb them through to the underlying Docker Client: PullParent and NoCache.

I realize that I could (should?) explicitly version the base image in the Dockerfile. But for some things, I just want to deploy the latest stable version once a week, for example.

Affected area/feature

Pulumi Docker Provider

[t0yv0]

Thanks for filing this @jdahlq ! This indeed sounds like a great improvement.

Anyone interested in this issue: upvoting helps my team prioritize; we're also open for contributions and can help shepherd a PR if anyone is interested.

Docker.Image is currently hand-crafted and not mapped to the upstream provider but it is possible to enhance its functionality.

CC @guineveresaenger in case you are aware of any duplicate requests for this.

[jdahlq]

I can take a crack at it if you'd like. Since it is hand-crafted, I assume I'd need to manually plumb it through to all the SDKs? Looking through the recent commits, this one that adds platform support looks like a good example for me to use?

[t0yv0]

Yes that looks like a good example, thank you! You don't need to do anything special for SDKs as they will be re-generated from the schema. Much appreciated!

[blampe]

Hi @jdahlq, we just released a new Docker Build provider focused exclusively on building images with buildx/BuildKit. It provides --pull and --no-cache functionality out of the box, and we recommend you use it for building images going forward. Please take a look and give us feedback!

The repository is here; our blog announcement is here; and finally API docs are here along with examples of how to migrate your existing Image resources to dockerbuild.Image.

We won't be able to add this functionality in this provider for a number of reasons, so I'm closing this as wont-fix.