Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Testing process.terminal? #109

Open
wking opened this issue Jun 13, 2016 · 2 comments
Open

Testing process.terminal? #109

wking opened this issue Jun 13, 2016 · 2 comments

Comments

@wking
Copy link
Contributor

wking commented Jun 13, 2016

#66 currently checks the terminal box with a reference to this code setting terminal to false in the default template. Grepping through the current master doesn't turn up anything that looks like tests though:

$ git describe --always
0b5e2eb
$ git grep -i terminal | grep -v Godeps
generate.go:            spec.Process.Terminal = context.Bool("tty")
generate.go:                    Terminal: false,

I think the current spec wording is untestably vague, and there's a recent runtime-spec issue that agrees (opencontainers/runtime-spec#494). One possible outcome is dropping the property from the spec. But in the face of all this uncertainty, I expect we want to:

  • Uncheck the terminal box in runtimespec VS ocitools #66 (ping @liangchenye).
  • Avoid testing the property until we have testable language for it in the spec, and understand if/why we are going to keep it in the spec.
@liangchenye liangchenye mentioned this issue Jun 26, 2016
76 tasks
@liangchenye
Copy link
Member

@wking sorry for being late, #66 was updated.

@wking
Copy link
Contributor Author

wking commented Aug 20, 2016

Cross linking upstream improvements in this area, there is work on clarifying the container side of terminal in opencontainers/runtime-spec#518, and after that lands there are plans to address the host side in opencontainers/runtime-spec#513. The API side is tied up with what runC can support, and that is being discussed in opencontainers/runc#814.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants