Nicolas De loof

before considering feasability and syntax to support this, I'd like to understand the benefits having such a feature. Actually I'd prefer we get a generic introspection mechanism for a container...

@dbwodlf3 are you running those agents as replicas for a single service? How would `hostname` help you managing a died agent? Don't you just restart it with `compose up`?

Closing this feature request as "not planed" as there's no clear use-case requiring such a change. Feel free to open a follow-up issue if you have one you can share

AFAICT this is already supported with latest codebase: https://asciinema.org/a/oJ5LmjJViKmx6COQTPEOTsTzP

I agree it would be nice to have `DOCKER_COLORS` to apply to all docker commands. It would then require https://github.com/moby/buildkit/pull/2954 to be an exported codebase in docker/cli (or a dedicated...

Can you please confirm you don't get the same issue using plain `docker buildx build https://github.com/...` command ? You can force compose to run the "classic" builder by setting `DOCKER_BUILDKIT=0`

I ran a quick test: - I created a private git repository set on gitlab.com - I created a personal access token - configured git to cache this access token...

How would `docker compose up` handle this, if you configure build output to write image to a local tar file, to create a container for service after a successful build...

created a draft PR to add support for custom build outputs, please give it a try and let me know if this covers your need https://github.com/docker/compose/pull/10642

@Aarbel your comment is unrelated to custom build output, feel free to open a dedicated issue (and include `docker inspect eca...` for diagnostic