Fix run action to respect COMPOSE_IGNORE_ORPHANS environment variable

[vaab]

It seems that COMPOSE_IGNORE_ORPHANS is not checked when using compose run which is quite cumbersome : people are more likely to use compose run for run-once CLI scripts and would then care about the outputs (stdout and stderr), they might not want to see warning about orphans poping out.

As I was not sure this was something you might want, tell me if I need to write tests or documentation.

[GordonTheTurtle]

Please sign your commits following these rules:
https://github.com/moby/moby/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:

$ git clone -b "run_ignore_orphans" git@github.com:0k/compose.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.

[ndeloof]

Seems legitimate to me and not a risky change.

[ulyssessouza]

Hello @vaab ! Thank you for the contribution!
Could you please add tests to your PR?

[redcinelli]

Hello @vaab ! Thank you for the contribution!
Could you please add tests to your PR?

I am keen on taking on the testing, but @ulyssessouza could you please help me out.

What should we be testing ? Some test on the project.up() already exist with the ignore_orphans set to either values.
And I don't think you want us to test toplevel_environment.get_boolean('COMPOSE_IGNORE_ORPHANS')

So I feel this behavior is already covered.
Which makes me a bit confused. 😅

[Wirone]

Can't believe it's still open after 2 years 🤯

[glours]

Thanks for taking the time to create this issue/pull request!

Unfortunately, Docker Compose V1 has reached end-of-life and we are not accepting any more changes (except for security issues). Please try and reproduce your issue with Compose V2 or rewrite your pull request to be based on the v2 branch and create a new issue or PR with the relevant Compose V2 information.