#1060666 podman-compose: Version is too old and fails to work

#1060666#5
Date:
2024-01-12 10:43:46 UTC
From:
To:
Dear Maintainer,

I tried to use the Debian package podman-compose with this code:

https://github.com/UB-Mannheim/quiver-benchmarks/tree/fixes

podman-compose was able to build a container, but each time when
I want to run it with `podman-compose run [...]`, it again builds
a new container, starts the application and terminates again.

I then tried an installation of podman-compose from PyPI.
That newer version works fine.

Therefore I think it would be good to update the version which
is provided by Debian, too.

#1060666#10
Date:
2024-01-15 20:01:49 UTC
From:
To:
podman-compose 1.0.6-1~bpo12+1 from bookworm-backports works fine.

I suggest to update bookworm to that version.

#1060666#15
Date:
2024-03-27 14:13:58 UTC
From:
To:
I've tested the github repository you cited and wasn't able to reproduce it
at all. Tested versions said to be working and the code still was really
unstable even using docker compose.

I believe this code you used wasn't the best example as I found its
Makefile really unstable with many versions of podman compose and even
Docker.

So I think this is not a issue with the version in Debian stable

#1060666#20
Date:
2024-08-20 12:34:31 UTC
From:
To:
Thanks for the report!

Would you mind providing the logs and a reproducer for the bug you are
seeing? While I understand the package version in bookworm is older and
lacks some features, I am not sure I agree it is unusable or completely
broken.

The basic examples are functional (see the ones at
/usr/share/doc/podman-compose/examples).

Also, would you mind providing a smaller reproducer? Running this
example requires an insane amount of space for the base image it is
pulling (there is a single layer > 10GB [4abe712135ae]). Hence, I could
not test your example, but I assume João did and could not reproduce it.

Until then, I am lowering the severity here to normal.