Eric Hripko
Eric Hripko
Is this something that already doesn't work in practice then, but just needs to be clarified?
Thank you for sharing this feedback @ciaranmcnulty 👍 As @tonistiigi points out, runtime platform can be a subset of build platforms. For example, you may be building for `arm` and...
Seems like there's a broad agreement on this 🎉 For the short-term, it makes sense to me that we replace `and/or` with `and` in the spec for clarity.
It only got approved recently, so I don't think `docker-compose` implementation caught up yet. In general, I think we can address some of the compatibility/support aspects of the spec with...
Hi @imthenachoman, see this [SO page](https://stackoverflow.com/questions/1962094/what-is-the-sign-off-feature-in-git-for) for more details.
Should we amend the wording on the spec to reflect this?
Hi @ericslandry - thank you for sharing this feedback 👍
Thank you for sharing this feedback @kendru 👍 This sounds like a potential bug in the Compose implementation. For instance, attributes like `network_mode` explicitly take `service:` or `container:CONTAINER` when it's...
Potentially conflicts with #147
If we consider GitHub-produced pages, then ToC is already generated from the content (see https://compose-spec.github.io/compose-spec/spec.html).