compatible with multiple runtimes
kata-runtime or cc-runtime has many limitations, referring to
https:/
1. stats
#docker stats testkata
CONTAINER CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS
testkata -- -- / -- -- -- -- --
2.top
#docker top testkata
Error response from daemon: rpc error: code = 13 desc = get all pids for container: unexpected end of JSON input
3.update
#docker update --cpus 2.0 testkata
Error response from daemon: Cannot update container 1ba556259715502
4. docker run --privileged
5. more
Blueprint information
- Status:
- Complete
- Approver:
- hongbin
- Priority:
- Medium
- Drafter:
- feng.shengqin@zte.com.cn
- Direction:
- Approved
- Assignee:
- feng.shengqin@zte.com.cn
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- hongbin
- Completed by
- hongbin
Related branches
Related bugs
Sprints
Whiteboard
(hongbin 2018-08-08): In general, I agree that we want to support multiple runtimes. I am not sure how to address the limitations of kata runtimes though. Perhaps, remove the API endpoints that kata don't support? Feel free to propose if you have any idea.
This feature is already supported:
* At client side, there is a --runtime option to specify a runtime (admin-only)
* At server side, scheduler supports a runtime filter that will pick a compute node with the right runtime.
* Individual compute node has a config option CONF.container_
-- hongbin 2020-04-19
