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
In other dockerized Rails apps, I'm able to throw a byebug/byebugger line in the code I'm testing, then send a request to the controller that I'm testing, verify the logs that byebug halted the execution, then I can do docker attach CONTAINERNAME to tap into byebug and do my stuff. But with this setup looks like I cannot do that: once I run docker attach, it gets stuck, and the only thing I can do is ctrl p-q to send an escape sequence.
I've already tried adding in compose.yaml stdin_open: true - in addition to tty: true which is already present.
Can you please help me with this?
The text was updated successfully, but these errors were encountered:
In other dockerized Rails apps, I'm able to throw a byebug/byebugger line in the code I'm testing, then send a request to the controller that I'm testing, verify the logs that byebug halted the execution, then I can do
docker attach CONTAINERNAME
to tap into byebug and do my stuff. But with this setup looks like I cannot do that: once I run docker attach, it gets stuck, and the only thing I can do is ctrl p-q to send an escape sequence.I've already tried adding in compose.yaml
stdin_open: true
- in addition totty: true
which is already present.Can you please help me with this?
The text was updated successfully, but these errors were encountered: