-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Error/Panic when no TTY present #253
Comments
wagoodman
added a commit
that referenced
this issue
Nov 22, 2019
Is this the same issue?
|
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
From @1138-4eb (#233 (comment))
Two different variants of this error:
The first one is because there is no tty and dive does require it (unless in CI mode). Hence, I would suggest to add a message/note when this error is handled and dive is being executed inside a container. I believe I have some golang function to detect this latter condition, but I don't know where is the error reported in the codebase. The message would suggest users to use -t (and -i?).
The second type of error might be trickier. Of course, dive should not crash, but exit gracefully. Apart from that, I don't think that any specific message can be shown. Requiring winpty is specific to some platforms/terminals, and there is no easy mechanism to identify the context from inside the container. A generic message may be added, tho.
The text was updated successfully, but these errors were encountered: