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
Docker handles the key sequence C-p C-q as a way of detaching from the running container if you're inside a PTY. This means it closes the PTY, but leaves the container running, so you can re-attach later.
Currently if you do that in fig, you'll appear to have 'locked' your terminal until you press Ctrl-C. This is because fig includes a call to client.wait(container), which will wait indefinitely on a detached session.
I'm not 100% what the correct approach is to fix this. I'm just documenting the issue and pointing to where the problem is.
The text was updated successfully, but these errors were encountered:
It would be nice to have C-p C-q to detach from the container(s) after running fig up and forgetting the -d flag, or within fig logs as I don't see a way to go in and out without bringing down the environment
This has been open for a while and there's been very little interest in this feature, so I think we can close this.
I think the detach from logs or up is more compelling. Might be worth opening a new issue for that. I'd personally like to make that behaviour the default.
Docker handles the key sequence C-p C-q as a way of detaching from the running container if you're inside a PTY. This means it closes the PTY, but leaves the container running, so you can re-attach later.
Currently if you do that in fig, you'll appear to have 'locked' your terminal until you press Ctrl-C. This is because fig includes a call to
client.wait(container)
, which will wait indefinitely on a detached session.I'm not 100% what the correct approach is to fix this. I'm just documenting the issue and pointing to where the problem is.
The text was updated successfully, but these errors were encountered: