This message was deleted.

I’m not the top expert on docker, but I think this is because

latest

is just a label as any other (like

v1.1

) and does not have a meaning like: go and get me the latest image you can find. So if there is one with the label

latest

already on your system, then it will use that one. This has nothing to do with pulumi I think.

🤔

so you created a new image on a different system, pushed it up to the registry and then tried to pull it to your local system?

I just tried to pull a public image which I know was not on my local system

hmm, then I don’t know either

It looks like it just queries the remote server and retrieves information:

OUTPUT               VALUE
    alpine_remote_image  {"build":null,"force_remove":null,"id":"sha256:6dbb9cc54074106d46d4ccb330f2a40a682d49dda5f4844962b7dce9fe44aaecalpine:latest","keep_locally":null,"latest":"sha256:6dbb9cc54074106d46d4ccb330f2a40a682d49dda5f4844962b7dce9fe44aaec","name":"alpine:latest","output":null,"pull_trigger":null,"pull_triggers":null,"urn":"urn:pulumi:staging::nozzle-insights-content-aggregator::docker:index/remoteImage:RemoteImage::alpine-remote-image"}

@quiet-truck-58459 are you running

pulumi up

or

pulumi preview

?

@broad-eve-12764 I've tried it with both.

I'm running into an issue where digest is different in remote repo, I think different repos define digests differently

Looking at the digest of the remote repo it appears to be using a tag