Guillaume Lours

I just opened an [PR](https://github.com/compose-spec/compose-spec/pull/272) and remove some confusion around the format of `ports.published` attribut

That's true if you're using Golang but it isn't regarding [Rust conventions](https://doc.rust-lang.org/std/env/consts/constant.OS.html) for example. Currently most of the implementations of the spec are done in Go but we should keep...

@jheld feel free to provide feedback on the #238 PR and https://github.com/compose-spec/compose-go/pull/236

@thaJeztah introduced in compose-go with this [PR](https://github.com/compose-spec/compose-go/pull/230), new versions of Compose can handle both, the issue comes when an older than `v2.3.0` version of Compose try to parse the `ports.published`...

@totalhack @fedde-s the release of Compose `v2.11.2` done yesterday should fix the issue, no workaround needed it should work without overriding the command

@crazy-max any idea ☝️ Do you have the same kind of e2e tests on the buildx side and if yes how did you address this issue?

@williamdes you can use the `docker` image which contains the latest version of Compose ```shell > docker run -it docker compose version Unable to find image 'docker:latest' locally latest: Pulling...

@williamdes did you try to replace `docker/compose` by `docker/docker` in your Dockerfile?

Can you post the output of `docker-compose version` with a dash please? Something is strange in you logs output, the `docker info` mentioned a version `v2.10.2` of Compose and the...

Hello @tronicboy1 Can you confirm that you wasn't using Compose v1 as @milas mentioned? If you are using Compose v2, could you test with the latest release, I think this...