mirror of
https://github.com/kata-containers/kata-containers.git
synced 2025-04-27 19:35:32 +00:00
In some cases, network endpoints will be configured through Prestart Hook. So network endpoints may need to be added(hotpluged) after vm is started and also Prestart Hook is executed. We move pre-start hook functions' execution to sandbox_start to allow hooks running between vm_start and netns_scan easily, so that the lifecycle API can be cleaner. Signed-off-by: Yushuo <y-shuo@linux.alibaba.com> |
||
---|---|---|
.. | ||
arch-images | ||
architecture | ||
architecture_3.0 | ||
data | ||
proposals | ||
agent-systemd-cgroup.md | ||
core-scheduling.md | ||
direct-blk-device-assignment.md | ||
end-to-end-flow.md | ||
hooks-handling.md | ||
host-cgroups.md | ||
inotify.md | ||
kata-2-0-metrics.md | ||
kata-api-design.md | ||
kata-design-requirements.md | ||
kata-nydus-design.md | ||
README.md | ||
vcpu-handling.md | ||
vcpu-threads-pinning.md | ||
virtualization.md | ||
VSocks.md |
Design
Kata Containers design documents:
- Kata Containers architecture
- API Design of Kata Containers
- Design requirements for Kata Containers
- VSocks
- VCPU handling
- VCPU threads pinning
- Host cgroups
- Agent systemd cgroup
Inotify
supportHooks
support- Metrics(Kata 2.0)
- Design for Kata Containers
Lazyload
ability withnydus
- Design for direct-assigned volume
- Design for core-scheduling