This message was deleted.

A few questions: 1. Can you post some details about what's failing? (Which step, and what's the Pulumi output?) 2. Does it have to be done in Pulumi, at least right now? Could you write a bash script that does what you need and optionally call it with the Command provider if it needs to be in Pulumi itself?

1. Josh, the image is not getting created/pushed to dockerhub. from the logs I get from this function, it shows the config being used by pulumi to create the docker image i.e.

+ docker:index/image:Image: (create)
        [urn=urn:pulumi:dev::<stack name>::docker:index/image:Image::<username>/node:18-buster-slim-arm-debian-latest]
        build    : {
            args         : {
                BUILDKIT_INLINE_CACHE: "1"
                platform             : "linux/amd64"
            }
            context      : "."
            contextDigest: <digest>
            dockerfile   : "Dockerfile.dev"
            platform     : "linux/amd64"
        }
        imageName: <image-name>
        registry : {
            password: <password>
            server  : "<https://index.docker.io/v1>"
            username: <username>
        }
        skipPush : false
msg="Successfully built and pushed Docker image with ID <username>/node:18-buster-slim-amd-debian-latest" imageID="<username>/node:18-buster-slim-amd-debian-latest" imageName="<username>/node:18-buster-slim-amd-debian-latest" platform=linux/amd64

2. This project involves a set of steps/configs which are added to the docker image. We are trying to write it in go as much as possible. We were prev. using the docker client SDK for go to build the image, but the docker SDK for go does not support creating manifests (for building multi-arch images). From the github issue, I thought that pulumi's SDK allows us to create manifest and so we thought of using pulumi.

Hi @sparse-umbrella-88444 - I am wondering if you are running into a version of https://github.com/pulumi/pulumi-docker/issues/812 or possibly awaiting changes underway in https://github.com/pulumi/pulumi-docker/pull/828. If you have verified an image is not being pushed to the registry despite logs telling you otherwise, it is worth filing a bug.

@sparse-umbrella-88444 Did I send you the link to how we are doing those multi-platform images for our own containers? Of course, this is in GHA, but you might find it useful as a reference for what you're trying to do: https://github.com/pulumi/pulumi-docker-containers/blob/main/.github/workflows/release.yml#L157-L230

@shy-arm-32391 could be this issue itself https://github.com/pulumi/pulumi-docker/issues/812 i.e. there's no error logs and I can't find the image in the registry.

Create the manifests using the

docker

CLI, since that seems to be the only way.

It sounds like there's two issues here: • unable to annotate local images with manifests (this is not something Pulumi can do at this moment and is marked as experimental in the official Docker docs) • image not getting pushed to registry I'm not confident this is an instance of https://github.com/pulumi/pulumi-docker/issues/812. If you have a minimum viable repro for us, we would appreciate it very much, because so far we have not been able to reproduce #812 reliably. I will look into the status of https://github.com/pulumi/pulumi-docker/pull/828 and see if we can release a patch once merged. Once you can push images, a manifest will be created automatically and you can query it via

docker manifest inspect

and you should be able to leverage pulumi-command to create the multi-arch image in the way you'd expect.