containers
Exit codes
Failure exit codes for build and push are currently not forwarded as exit code for podman-compose. This makes it impossible to use podman-compose in a scripted environment like CI.
With this PR, podman-compose stops building/pushing when the underlying podman command fails and forwards its exit code.
Want to put +1 vote for this, this is really annoying.
Here's the example of how it looks like (podman machine is stopped, so it produces error).
@ebekebe looks like other commands (like run) also suffers from this. Or am I missing something? Why did you choose to fix just these?
@mi-volodin I didn't notice that other commands also don't work. I would have included them at the time. However, we don't use podman-compose (and podman) anymore, because of how it is maintained. As there is no feedback from a project maintainer yet, I don't want to put any more effort into this. Feel free to make your own PR or add you changes to this PR. Let me know, if you want push access.
Seems like the issue fixed by this PR is still present at least for some commands.
@ebekebe Would you be open to rebase the PR?
This PR is no longer needed after https://github.com/containers/podman-compose/pull/1259 landed.