4887ce059c
Changes: 96be8229 release: Release v0.7.0 5115ad6e vmm: config: Support on/off/true/false for all booleans d5bfa2df vmm, vhost_user_block: Make parameter names match --disk 2f0bc06b vmm: Update default devices names as "internal" aaba6e77 vmm: Add virtio-console to the list of Migratable devices 9ab4bb1a devices: serial: Expect an identifier upon device creation 06487131 vm-virtio: pci: Expect an identifier upon device creation eeb7e10d vm-virtio: mmio: Expect an identifier upon device creation 9d84ef50 vmm: Make the virtio identifier mandatory 14350f5d devices: ioapic: Expect an identifier upon device creation 55687157 vm-virtio: iommu: Expect an identifier upon device creation 052eff1c vm-virtio: console: Expect an identifier upon device creation 354c2a4b vm-virtio: vhost-user-net: Expect an identifier upon device creation 46e0b3ff vm-virtio: vhost-user-blk: Expect an identifier upon device creation bb7fa71f vm-virtio: vhost-user-fs: Expect an identifier upon device creation ec5ff395 vm-virtio: vsock: Expect an identifier upon device creation 9b53044a vm-virtio: mem: Expect an identifier upon device creation 1592a929 vm-virtio: pmem: Expect an identifier upon device creation 2e91b738 vm-virtio: rng: Expect an identifier upon device creation 9eb7413f vm-virtio: net: Expect an identifier upon device creation be946caf vm-virtio: blk: Expect an identifier upon device creation ff9c8b84 vmm: Always generate the next device name 81831413 vmm: Add an identifier to the ioapic device e4386c8b vmm: Add an identifier to the virtio-iommu device 75ddd2a2 vmm: Add an identifier to the --console device eac350c4 vmm: Add an identifier to the virtio-mem device 6802ef54 vmm: Add an identifier to the --rng device d71d52e9 vmm: Fix virtio-console creation with virtual IOMMU b08fde59 vmm: Fix virtio-rng creation with virtual IOMMU 8031ac33 vmm: Fix virtio-vsock creation with virtual IOMMU 50134969 Jenkins: Run musl unit and integration tests on master branch ce794f78 ci: Pass target triple to the test scripts 33b0e158 resources: Add musl tools and toolchain to the Dockerfile ad9374bd dev_cli: Add --libc to the build and test commands 8cef3574 vmm: seccomp: Add fork, gettid and pipe2 syscalls to permitted list ce7678f2 vmm: seccomp: Add tkill syscall to permitted list 12758d7f vmm: seccomp: Add epoll_pwait syscall to permitted list 86fcd19b build: Initial musl support a5de4955 vmm: Only allow removal of specific types of virtio device 9ed880d7 vmm: Add an identifier to the --fs device 7e0ab6b5 vmm: Fix pmem device creation 3012975c tests: Enhance vsock integration test to support hotplug 6c2bca5f bin: ch-remote: Add support for adding vsock devices 8de7448d vmm: api: Add "add-vsock" API entry point bf09a1e6 openapi: Add "id" field to VsockConfig a76cf086 vmm: vm: Remove vsock device from config 99422324 vmm: vm: Add "add_vsock()" 1d61c476 vmm: device_manager: Add support for hotplugging virtio-vsock devices f8501a3b vmm: config: Move --vsock syntax to VsockConfig 6e049e0d vmm: Add an identifier to the --vsock device 10348f73 vmm, main: Support only zero or one vsock devices 9d1f95a3 openapi: Add missing "id" field 30e2e515 build(deps): bump serde_json from 1.0.51 to 1.0.52 dd9d0d04 build(deps): bump micro_http from `0d87a94` to `c9ffb90` cdc8493a build(deps): bump thiserror from 1.0.15 to 1.0.16 Fixes: kata-containers/runtime#2658 Signed-off-by: Bo Chen <chen.bo@intel.com> Signed-off-by: Peng Tao <bergwolf@hyper.sh> |
||
|---|---|---|
| .github | ||
| ci | ||
| src | ||
| tools/osbuilder | ||
| .gitignore | ||
| .travis.yml | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| VERSION | ||
Kata Containers
Welcome to Kata Containers!
The purpose of this repository is to act as a "top level" site for the project. Specifically it is used:
-
To provide a list of the various other Kata Containers repositories, along with a brief explanation of their purpose.
-
To provide a general area for Raising Issues.
Raising issues
This repository is used for raising issues:
-
That might affect multiple code repositories.
-
Where the raiser is unsure which repositories are affected.
Note:
- If an issue affects only a single component, it should be raised in that components repository.
Kata Containers repositories
CI
The CI repository stores the Continuous Integration (CI) system configuration information.
Community
The Community repository is the first place to go if you want to use or contribute to the project.
Code Repositories
Kata Containers-developed components
Agent
The kata-agent runs inside the
virtual machine and sets up the container environment.
KSM throttler
The kata-ksm-throttler
is an optional utility that monitors containers and deduplicates memory to
maximize container density on a host.
Proxy
The kata-proxy is a process that
runs on the host and co-ordinates access to the agent running inside the
virtual machine.
Runtime
The kata-runtime is usually
invoked by a container manager and provides high-level verbs to manage
containers.
Shim
The kata-shim is a process that
runs on the host. It acts as though it is the workload (which actually runs
inside the virtual machine). This shim is required to be compliant with the
expectations of the OCI runtime
specification.
Additional
Hypervisor
The qemu hypervisor is used to
create virtual machines for hosting the containers.
Kernel
The hypervisor uses a Linux* kernel to boot the guest image.
Documentation
The documentation repository hosts documentation common to all code components.
Packaging
We use the packaging repository to create packages for the system components including rootfs and kernel images.
Test code
The tests repository hosts all test code except the unit testing code (which is kept in the same repository as the component it tests).
Utilities
OS builder
The osbuilder tool can create a rootfs and a "mini O/S" image. This image is used by the hypervisor to setup the environment before switching to the workload.
Web content
The www.katacontainers.io repository contains all sources for the https://www.katacontainers.io site.
Credits
Kata Containers uses packagecloud for package hosting.