Nicolas De loof
Nicolas De loof
Added a test case pulling a docker app of mine. some additional notes without extended Accept header, multi-arch docker image `busybox` manifest is served by DockerHub as `application/vnd.docker.distribution.manifest.v2+json`: ```json {...
Just notice this PR is duplicating https://github.com/genuinetools/reg/pull/191
compose-go is not just a drop-in replacement for legacy compose support in docker/cli, so this change will require some extra testing for backward compatibility. https://github.com/docker/cli/pull/3257 will provide a temporary workaround
> I don't even know how it'd be possible to use Swarm secrets without versioning them, which in turn isn't possible without variables in the compose file ... A potential...
compose v2.0.1 includes native support to be used as a drop-in replacement for `docker-compose` binary with command line translation, so AFAICT this repo doesn't need to produce binaries anymore and...
This design decision came late, so the outdated documentation Makes me wonder we should just get the `convert` logic moved to docker/compose and archive this repo?
@francislavoie I left Docker, so I can't tell about decision on linux packaging cc @ulyssessouza @thaJeztah
cc @ulyssessouza
Sure, then just setup your PATH to pick up compose-switch before legacy docker-compose V1.
Compose V2 binary 2.0.1 actually includes some of the logic from this repo and can be used directly as `docker-compose` binary in your path