Error: --platform or --push not supported w/dockerComposeFile

[metaskills]

I noticed that the ci project now supports a platform option with the following work devcontainers/ci#175 However, it breaks for me when I use this with dockerComposeFile. I can reproduce this locally too with the CLI.

(kencollins) - (~/Repositories/lamby-citest) 💎 3.1.3 🔄 main
> devcontainer build --workspace-folder . --image-name test --platform linux/amd64
[16 ms] @devcontainers/cli 0.29.0. Node.js v18.11.0. darwin 21.6.0 x64.
Error: --platform or --push not supported.
    at uoe (/Users/kencollins/.nodenv/versions/18.11.0/lib/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:2045:27034)
    at async aoe (/Users/kencollins/.nodenv/versions/18.11.0/lib/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:2045:25017)
{"outcome":"error","message":"--platform or --push not supported.","description":"--platform or --push not supported."}

Is this an oversight on behalf of the following work where some error handling needs to be removed?

• Add multi build support #24
• Build command: Support multiple --image-name parameters  #61

I tracked the error to the following location in the code. Thoughts?

• https://github.com/devcontainers/cli/blob/main/src/spec-node/devContainersSpecCLI.ts#L585-L589

[eduardolat]

+1

[AlexKeySmith]

I've noticed the feature request tag being added, I presume this means that docker compose based devcontainers aren't able to be built for separate platforms? It would be helpful for readers to be able to understand the constraints and alternative approaches.