Open pitrou opened 2 months ago
+1
Hmm, there's also a ARCHERY_USE_DOCKER_BUILDX option that allows building an image using docker buildx
instead of docker build
. I don't know how useful it is.
At the time of the development docker's ecosystem across the various platforms was rather fragmented, some of the tools were better in caching (I mean they had proper cache hits) but not available on certain platform. We also used archery ok self hosted machines where these options were handy (compose for example didn't have cache hits on self hosted machines but plain docker had). I believe these differences are now gone, so I think both docker-compose and buildx related options and flags can be safely removed.
Let's deprecated both of ARCHERY_USE_DOCKER_CLI
and ARCHERY_USE_DOCKER_BUILDX
.
Describe the enhancement requested
The ARCHERY_USE_DOCKER_CLI originally avoids using the
docker-compose
utility and using thedocker
CLI directly instead. However, with #43608 now fixed, our usage ofdocker-compose
has mostly been replaced with thedocker compose
subcommand which should fix the issues and shortcomings ofdocker-compose
. Therefore, ARCHERY_USE_DOCKER_CLI may have become irrelevant.@kou @kszucs Thoughts?
Component(s)
Archery, Continuous Integration