docs/terminals.md: add troubleshooting #2985
Conversation
docs/terminals.md
Outdated
| ``` | ||
|
|
||
| from runc, it means it can't open a terminal (because there isn't one). This | ||
| can happen in case stdin (and possibly also stdout and stderr) are redirected, |
There was a problem hiding this comment.
| can happen in case stdin (and possibly also stdout and stderr) are redirected, | |
| can happen when stdin (and possibly also stdout and stderr) are redirected, |
docs/terminals.md
Outdated
|
|
||
| from runc, it means it can't open a terminal (because there isn't one). This | ||
| can happen in case stdin (and possibly also stdout and stderr) are redirected, | ||
| or on some environments that lack a tty (such as GitHub Actions runners). |
There was a problem hiding this comment.
| or on some environments that lack a tty (such as GitHub Actions runners). | |
| or in some environments that lack a tty (such as GitHub Actions runners). |
docs/terminals.md
Outdated
| can happen in case stdin (and possibly also stdout and stderr) are redirected, | ||
| or on some environments that lack a tty (such as GitHub Actions runners). | ||
|
|
||
| The solution to this is *not* use a terminal for the container, i.e. have |
There was a problem hiding this comment.
| The solution to this is *not* use a terminal for the container, i.e. have | |
| The solution to this is to *not* use a terminal for the container, i.e. have |
docs/terminals.md
Outdated
|
|
||
| The solution to this is *not* use a terminal for the container, i.e. have | ||
| `terminal: false` in `config.json`. If the container really needs a terminal | ||
| (as some programs require it), you can provide one, using one of the following |
There was a problem hiding this comment.
| (as some programs require it), you can provide one, using one of the following | |
| (some programs require one), you can provide one, using one of the following |
docs/terminals.md
Outdated
| (as some programs require it), you can provide one, using one of the following | ||
| methods. | ||
|
|
||
| One way to do so is to use `ssh -tt` option. The second `t` forces a terminal |
There was a problem hiding this comment.
| One way to do so is to use `ssh -tt` option. The second `t` forces a terminal | |
| One way is to use `ssh` with the `-tt` flag. The second `t` forces a terminal |
docs/terminals.md
Outdated
|
|
||
| One way to do so is to use `ssh -tt` option. The second `t` forces a terminal | ||
| allocation even if there's no local one -- and so it is required when stdin is | ||
| not a terminal (known `ssh` implementations only look for a terminal on stdin). |
There was a problem hiding this comment.
| not a terminal (known `ssh` implementations only look for a terminal on stdin). | |
| not a terminal (some `ssh` implementations only look for a terminal on stdin). |
docs/terminals.md
Outdated
| allocation even if there's no local one -- and so it is required when stdin is | ||
| not a terminal (known `ssh` implementations only look for a terminal on stdin). | ||
|
|
||
| Another way is to run runc under `script` utility, like this |
There was a problem hiding this comment.
| Another way is to run runc under `script` utility, like this | |
| Another way is to run runc under the `script` utility, like this |
docs/terminals.md
Outdated
| $ script -e -c 'runc run <container>' | ||
| ``` | ||
|
|
||
| Note that older versions of `script` are known to have issues. |
There was a problem hiding this comment.
Can you provide a bit more detail about what kinds of issues?
Explain where the "/dev/tty: no such device or address" error is coming from, and provide ways to solve the issue. Signed-off-by: Kir Kolyshkin <[email protected]>
|
Addressed review comments, thanks @cyphar |
|
I'm not sure what's happening but it seems that GitHub comments system is having issues. I see review comments being repeated, and I don't see the replies that I left. |
I think the biggest issue for me was that There was some occasional lockups as well, but I am not sure if this was script. Anyway, since this description is so vague, I have removed this "beware of bugs" |
Explain where the "/dev/tty: no such device or address" error is coming
from, and provide ways to solve the issue.
For more background, see #2970