You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 17, 2023. It is now read-only.
Describe the bug
AFAIK, PRM is only able to work with tools that execute a command and exit. With tools like the puppet debugger that keep the input open there needs to be a way to stream the output back to the console and continue to forward input. Docker does not appear to be the issue since it can run a puppet debugger container just fine.
Describe the bug
AFAIK, PRM is only able to work with tools that execute a command and exit. With tools like the puppet debugger that keep the input open there needs to be a way to stream the output back to the console and continue to forward input. Docker does not appear to be the issue since it can run a puppet debugger container just fine.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The debugger console would prompt for input instead of just exit right away
Screenshots or logs
What versions are you running?:
Additional context
If I take the dockerfile generate above and create the image manually, then invoke it from the CLi the debugger works as expected.
The text was updated successfully, but these errors were encountered: