luciangabor

I don't know exactly since when, but it's been a while since it's possible to define the project's `name` as a top-level element in compose.yaml ... and this allows having...

v2.24.3? It's not yet released ... (I was actually hoping that the fix for #11377 fixes this randomness too, but that's now fixed in v2.24.2 and I still get the...

:( Maybe running inside a docker helps: ```yaml services: bug: build: dockerfile_inline: | FROM docker:${DOCKER_CLI_TAG:-cli} WORKDIR /root/src COPY

With a longer chain I consistently get the wrong path (dir instead of .): ```yaml services: bug: build: pull: true dockerfile_inline: | FROM docker:${DOCKER_CLI_TAG:-cli} WORKDIR /root/src COPY

Out of curiosity, are you sure that worked? Was "10.254.66.2:5432:5432/tcp" necessary? Isn't binding on 0.0.0.0 enough? Binding with the same port on 0.0.0.0 and another ip fails without compose (this...

> Explicit is better than implicit :-) > > Also when binding 0.0.0.0 I open it up to the public. While with a dedicated interface IP it can only be...

Perhaps the --env/-e could be added to the main set of compose options. It would allow to easily overwrite a variable, without relying on the shell (and I think Windows's...

Well, yes, there's no way around understanding where and how those variables are used.

While just trying to help (while benefiting from fixes/enhancements that are important to me), and trying to make the point that the ... point of the quoted statement from that...

I was testing this issue using the latest ci artifacts (https://github.com/docker/compose/actions/runs/8063698832) and stumbled upon a regression here's my setup: ```console $ find -name '*.yaml' -print -exec cat {} \; ./compose.yaml...