Open skateman opened 1 year ago
I traced this back to #425 and https://github.com/containers/podman-compose/commit/d6e21dc7523bd26b3526cdb7beb7c88c86c750f1, apparently --requires
doesn't take into account one-off containers :disappointed:
@skateman Hi! Did you manage to find a solution?
Not really, I am using docker-compose instead...colleagues went with donwgrading.
This issue is still seen
This is still an issue, just ran into it today trying to migrate a project from docker-compose to podman-compose.
Still an issue with using podman version: 4.9.4
Still an issue with using podman version: 4.9.4
Same here: https://github.com/taigaio/taiga-docker/issues/138
Any fix yet?
Describe the bug When a container depends on a one-off task container that depends on another container, e.g. a web server depending on DB migrations depending on a database, its dependency graph gets broken as soon as the one-off task exits, regardless of its exit code.
This issue was not present in version
1.0.3
and it was introduced in1.0.6
.To Reproduce
Expected behavior The first and third services run properly and the second one exits successfully.
Actual behavior The dependency graph gets broken as the third service depending on the second cannot be started.
Output
Environment:
Additional context