Nicolas De loof
Nicolas De loof
I can't reproduce. Can you share your compose file?
One possible reason is that some container are being started during the `up` sequence. To avoid conflict between container initial logs and progress UI, `Start` events are ignored so the...
@virtualstaticvoid unrelated, see https://github.com/docker/compose/issues/13420
Closing as "fixed by https://github.com/docker/compose/pull/13439" Maybe there's multiple UI issues here, so feel free to comment if you get some weird behavior which latest codebase (`make install` to test) doesn't...
Interesting proposal that would bump compose interpolation into a higher dimension. Anyway I wonder this is going too far, making compose file a development language on its own. I don't...
#248 proposal hasn't been approved nor debated yet, and while Kubernetes offers a weird self-reference mechanism relying on `fieldPath` doesn't mean we have to do the same.
I perfectly know the many limitations in the compose syntax, I'm just not convinced the "right" way to support those is to create a monster.
While I understand the frustration and don't like enthusiastic contributors to get frustrated, as a maintainer who will have to manage such a feature for the incoming years, I prefer...
Without a reproductible example I hardly can help here. Can you inspect container and network being created by Compose 2.40.3 and compare with earlier version ?
@iquito can you try using a plain `docker run --network xx alpine ping ` to check a non-compose container can communicate over network to your other service ? Then please...