-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Issue: Container keeps running after exit #694
Comments
If there is at least one fail during workflow then that container will not stop. |
Oh, this is a feature? Wasn't aware of that. |
Well, it certainly was "expected behaviour" from my point of view that containers don't exit although I've been thinking about making at least a flag to kill all containers, just haven't got around it yet. |
Keeping the container alive helps in debugging. |
I think there should be an option to either enable or disable this feature. Not sure what a sensible default would be, but I would bet for allow to enable this would be good. The default behavior of act shouldn't probably to debug something but to run a workflow. And when finished, every system resource should be freed. But thats just my take 😃 |
The default behaviour is always current behaviour unless something is completely broken currently. |
That's probably because you want to run the workflow and some people want to create an actions for GHA. It's reasonable for a container to not exit when it had issue so it could be debugged. |
Agreed, I use it to create actions... But I also think an argument to keep the container running will be good... like in CircleCI when you tell to keep ssh open to debug.. its not the normal usage but good to have it. Thanks!! |
This patch adds a new command-line flag (`--rm`) to automatically stop workflow container(s), just prior to exit. The default behavior is kept, e.g.: the containers continue running at exit. Fixes: nektos#694 Signed-off-by: Joseph Benden <joe@benden.us>
This patch adds a new command-line flag (`--rm`) to automatically stop workflow container(s), just prior to exit. The default behavior is kept, e.g.: the containers continue running at exit. Fixes: nektos#694 Signed-off-by: Joseph Benden <joe@benden.us>
This patch adds a new command-line flag (`--rm`) to automatically stop workflow container(s), just prior to exit. The default behavior is kept, e.g.: the containers continue running at exit. Fixes: nektos#694 Signed-off-by: Joseph Benden <joe@benden.us>
This patch adds a new command-line flag (`--rm`) to automatically stop workflow container(s), just prior to exit. The default behavior is kept, e.g.: the containers continue running at exit. Fixes: #694 Signed-off-by: Joseph Benden <joe@benden.us> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
I was looking for a way to keep the container running, and google brought me here. The relevant flag is
|
Thanks to @ggoretkin-bdai and his >1 year old comment, which has come in clutch for me. Is this and other flags listed on the docs site ( |
googling github act "--reuse" leads to no meaningful documentation
|
Act version
Expected behaviour
All containers started by act should be stopped/exit as soon as act terminates.
Actual behaviour
Not sure in which condition this happens, but some containers never exit.
Steps to reproduce
Not sure.
The text was updated successfully, but these errors were encountered: