-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Closed
Milestone
Description
Regarding the documentation, runc-rc1 (https://github.com/opencontainers/runc/releases/tag/v1.0.0-rc1) provide a new workflow based on 4 steps :
- create
- start
- kill
- delete
Readme specify that containers created with this new workflow have to be in "background mode" (terminal=false).
in the future, hooks will be removed from both in OCI and runC (see opencontainers/runtime-spec#483 and opencontainers/runtime-spec#483 for more info).
So how runC will handle the tty problem for terminal=true containers ?
I see three options here :
- Update the tty.go code to fit the new workflow
- Delegate tty management to users
- Use runc run for terminal=true containers
What is the "official" position of the runC dev team about this subject ?
Thanks for reading/answers
Metadata
Metadata
Assignees
Labels
No labels