-
Notifications
You must be signed in to change notification settings - Fork 475
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Podman compose is starting containers attached by default #563
Comments
I think it's on line 2059-2065 of podman_compose.py:
But I can't understand WHY you would force an G...C |
Removing the "-a" does in fact fix the issue for me. |
Suggested fix in Pull Request: |
@UnKulMunki I came across this issue while investigating another one I'm having with With
and it effectively starts my test container ( With current devel version of I tried to apply your patch from #564 and it expectedly changes the behavior - all my containers run detached, and (I'm incorporating some tooling into CI pipelines, and having test output in stdout/stderr is absolutely essential.) |
why not just pass |
@muayyad-alsadi The same scenario implemented surprisingly good in |
Describe the bug
the command :
podman-compose -f=compose.yml
is actually appending the '-a' switch to the start command:podman start -a <CONTAINER_NAME>
This is a problem because I am stuck staring at the the last container's log entries as they pop onto the screen. Only a CTRL-C gets me out of that and also kills the last container. or doing a
CTRL+Z
and thenbg
to send to to background processing. This is of course a problem because I am trying to script automated service building.To Reproduce
Steps to reproduce the behavior:
podman-compose -f=<DIR_NAME>/compose.yml up
Expected behavior
containers start in a detached mode by default unless a podman-start-args switch is given for -a or --attached
Actual behavior
the '-a' switch is being appended to the start commands for each container:
podman start -a <CONTAINER_NAME>
So I am stuck attached to the last container started
Output
Environment:
Additional context
I am trying to use podman-compose in automated container building for a CI / CD pipeline. Therefore getting stuck with attached containers is sub-optimal.
Thank you for your attention.
G...C
The text was updated successfully, but these errors were encountered: