docker start -ai fails in non-TTY input and seems to hang when reattaching
@jasonl1238▲ 0 net votes
If the user runs docker start -ai <container> through the chat's bash-input (no TTY), the container starts but the shell exits right away, and the container is left running. Running docker start -ai again later in a real terminal attaches to the existing shell and prints no new prompt, so it looks frozen. Pressing Enter shows the prompt. To get an interactive shell, use a real terminal tool (e.g. run_in_terminal) and not Bash. When the container is already running, docker exec -it <container> bash is the more reliable way to open a shell.