Using multi-arch Docker images with Pulumi?

[aterreno]

Hi all,
I think I've hit a bug with pulumi building docker images, I am trying to build a multiarch image, in order to do that I've setup my mac (M1) to use buildx by default.
When I add the --platform flag into the pulumi code I get back an error, that the command is not right.
If I copy the command and paste into the terminal as-is the docker build works...
I've put a very simple sample into github to reproduce https://github.com/aterreno/pulumi-docker-multiarch

What's the best repo to open an issue on github @pulumi/pulumi?

Or am I missing something else and it's not a bug?

Thanks

[mattstratton]

Tracking this issue in pulumi/pulumi-docker#296

Once this is resolved, we should update this post to help people in the future!

[ffMathy]

This is now resolved.

[mattstratton]

(I updated the title of this post and moved it to the providers category so that once we have the answer, it will work properly here! Thanks for posting it!!)

[aterreno]

really strange, all the code is doing is just pushing args

https://github.com/pulumi/pulumi-docker/blob/master/sdk/nodejs/docker.ts#L466

I don't see why that would work 🤔

[aterreno]

debugging further, if I log the command line params looks like:

["build","-f","./Dockerfile","--quiet","--platform","linux/amd64,linux/arm64,linux/arm/v7"]

[aterreno]

later on we endup doing a call to child_process.spawn with:

{"cmd":"docker","args":["build","-f","./Dockerfile","--quiet","--platform","linux/amd64,linux/arm64,linux/arm/v7",".","-t","e23d430b-container"]}

[aterreno]

I think I've got it, the child process doesn't understand that we are doing a docker buildx create --use before

This code works for example

const { spawn } = require("child_process");

const command = {
    cmd: 'docker',
    args: [
      'buildx',
      'build',
      '--platform',
      'linux/amd64,linux/arm64,linux/arm/v7',
      '.',
    ]
  }

const p = spawn(command.cmd, command.args, process.env);

p.stdout.on("data", (data) => {
  console.log(`stdout: ${data}`);
});

p.stderr.on("data", (data) => {
  console.error(`stderr: ${data}`);
});

p.on("close", (code) => {
  console.log(`child process exited with code ${code}`);
});

[aterreno]

so, remarkably probalby this works

import * as awsx from "@pulumi/awsx";

const repository = new awsx.ecr.Repository("test");

const image = repository.buildAndPushImage({  
  extraOptions: [
    `buildx`,
    `build`,
    '--platform',
    'linux/amd64,linux/arm64,linux/arm/v7',
  ],
});

module.exports = { image, repository };

but indeed, once you start specifying other params such as -f and so on the order is wrong, so it's not a viable workaround for most use cases.

[nimbinatus]

Adding a workaround from @stevesloka while the issue is still open:
pulumi/pulumi-docker#296 (comment)

I found a quick workaround for anyone needing to build linux/amd64 images on their m1-based macs. If you set the env variable DOCKER_DEFAULT_PLATFORM=linux/amd64 before your docker build (or any command), docker for mac will build the proper image for you.

This doesn't take the place of proper multi-arch builds, but if this can unlock anyone on m1's for now I wanted to share.