David Shrewsbury

Keep in mind that processing of `ARG` and `RUN` commands is performed by the container system (docker or podman), and not builder itself. Builder is mostly a front end to...

Sorry for taking so long to look at this... I'm unable to reproduce the behavior you are seeing. Here is the script I used, using what little sample you provided...

@superstes Thanks for that reproducer. While we investigate, you posted a private SSH key in the reproducer, exposing it to the Internet. So if that key is currently in use,...

Thanks for the report. After looking more closely, it looks like your regular expression for the BECOME password is incorrect, causing the hang. The prompt is actually: ``` BECOME password[defaults...

> Overall looks okay, though I'd question if it warrants a dedicated CLI arg- for most things we guard that kind of addition pretty carefully. Ack. I can remove that...

> @Shrews there's a corner case in Rich interpreting `FORCE_COLOR` as "also produce ANSI-sequences for bold" with `NO_COLOR` as "only disable color-related ANSI but not bold". > I decided that...

NOTE: The `tox-dev` framework we use in CI sets `FORCE_COLOR=1`. If we were to support that option, it would need to be at a lower priority than `NO_COLOR`, because otherwise...

See the comments under issue #1082. Basically, you need to use the `cmdline` keyword argument available in the `ansible_runner.run()` method to pass along options to do privilege escalation (example: `cmdline="-K...

Closing this as there has been no feedback for several months. If you are still having an issue, feel free to open a new issue with examples of where you...

A few initial questions: - Is this something new with version `2.4.0` or does it also occur with older versions of runner? - Any chance you have a simple reproducer...