Heads-up: new version of docker-compose heading to Tumbleweed
Hi all, just as a heads-up: I have updated the python-based version of docker-compose to the latest version available. And found out that there is a version 2.x which is a major rewrite in Go. I have package the new non-python docker-compose package as well as the docker-compose-switch one, as v2 drops the docker-compose binary, and compose is just a cli-plugin for docker. I.e. "docker compose version" instead of "docker-compose version". That is where the docker-compose-switch package comes into the picture, as it provides a compatibility helper, i.e. there will still be a docker-compose binary to call. Caveat: As v2 is no longer a standalone binary, this does no longer work with Podman instead of docker. That means, if you update your system, the python3-/python38-/python39-/python*-docker-compose package will be removed and the two new packages will be installed, together with docker and its dependencies if not yet present. If this not desired, the best approach would be to either switch to the python*-podman-compose package (that is actively maintained) or, if that is not possible, lock the existing python*docker-compose one. The submit requests are here: https://build.opensuse.org/request/show/987334 https://build.opensuse.org/request/show/987335 Feel free to review, add comments or point out errors. As for the Provides/Obsoletes/Requires handling the transition, there was a discussion on the packaging list where I finally got a solution that worked (at least for me) on both Tumbleweed and Leap 15.x. Feel free to test and report back any errors. Packages are here:
https://build.opensuse.org/project/show/home:ojkastl_buildservice:docker_com...
Have a lot of fun... ;-) Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
In data giovedì 7 luglio 2022 20:35:22 CEST, Johannes Kastl ha scritto: Hello,
As v2 is no longer a standalone binary, this does no longer work with Podman
Do you mean it is no longer possible to point it to the Podman socket?
The submit requests are here:
Given the nature of the change, it might be a good idea to do a follow-up mail once they are accepted in TW, so that people are aware when it's actually going to land. -- Luca Beltrame - KDE Forums team GPG key ID: A29D259B
Hi Luca, On 08.07.22 at 05:44 Luca Beltrame wrote:
In data giovedì 7 luglio 2022 20:35:22 CEST, Johannes Kastl ha scritto:
As v2 is no longer a standalone binary, this does no longer work with Podman
Do you mean it is no longer possible to point it to the Podman socket?
Unfortunately yes. It is a cli-plugin for the official docker command, hence it only works with the docker command.
The submit requests are here:
Given the nature of the change, it might be a good idea to do a follow-up mail once they are accepted in TW, so that people are aware when it's actually going to land.
Sure, will do that. Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
Il 08/07/22 08:20, Johannes Kastl ha scritto:
Unfortunately yes. It is a cli-plugin for the official docker command, hence it only works with the docker command.
Hmm... reading the docs[1] in principle one could do: docker -H unix:///path/to/podman.socket compose [options] and like that it may work? Unfortunately, it is all speculation as I don't have any system where I can test this using your packages (without breaking stuff that's running, that is). [1] https://docs.docker.com/engine/reference/commandline/cli/ -- Luca Beltrame GPG key ID: A29D259B
Hi Luca, On 08.07.22 at 08:32 Luca Beltrame wrote:
Hmm... reading the docs[1] in principle one could do:
docker -H unix:///path/to/podman.socket compose [options]
and like that it may work?
Unfortunately, it is all speculation as I don't have any system where I can test this using your packages (without breaking stuff that's running, that is).
[1] https://docs.docker.com/engine/reference/commandline/cli/
Yes, it could work. But in that case I would rather switch to podman and podman-compose, which worked fine in my tests (see below). Rather than having docker and podman installed, but not running the docker service but only use the executable to talk to podman, which normally does not have a daemon running and does not expose the socket by default, ... Kind Regards, Johannes P.S.: There is one exception with podman-compose: If you pipe the output of "podman-compose ... some command" to a file, you always get four extra lines with podman versions and stuff like that, which breaks some scripts. https://github.com/containers/podman-compose/issues/489 -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
participants (3)
-
Johannes Kastl -
Luca Beltrame -
Luca Beltrame