Nicolas De loof
Nicolas De loof
tested with Docker Compose version v2.2.2 `docker-compose kill` return 0 even when there's no container to kill
This has been (partially) fixed on the Compose-specification: https://github.com/compose-spec/compose-spec/pull/222 now need to get this also implemented in the code
Right, we should keep buildx dependency up to date. In an ideal world we should not vendor buildx in compose, but delegate to buildx as installed by the docker CLI......
I wonder: doesn't dependabot help us to address this?
:+1 `--no-color` should disable all uses of ANSI color sequences
Volume permission is very common issue with docker, and as long as you use bind mounts you even tell the engine "I'm in charge for this one, just expose inside...
we indeed are waiting for a docker/go-connections release so that we can bump dependency. @thaJeztah would it make sense to release v0.5.0?
We copy/pasted code from buildx as compose v2 was not yet an established long term plan for compose but we needed support for `build`. So it would make perfect sense...
on the other hand, being able to have variable expanse anywhere in the yaml tree is a major feature of compose ... IIRC you can use doubled dollar for this...
> Right, but the expansion shouldn't even happen here should it? How could we distinguish a user mistake to not declare a required variable vs a plain dollar sign? Also,...