For now, when we're using cache factory to launch kata containers,
we would encounter nil pointer runtime panic.
Fixes: #2272
Signed-off-by: Penny Zheng <penny.zheng@arm.com>
Many changes introduced by Archana Shinde.
This workflow will:
1. get a list of artifacts from the packaging repo
2. In parallel, build each of the applicable artifacts
3. Consolidate the build artifacts from <2>
4. Test the artifacts in a docker image on AKS
5. Push the verified docker image to dockerhub
Signed-off-by: Eric Ernst <eric.ernst@intel.com>
Signed-off-by: Archana Shinde <archana.m.shinde@intel.com>
Don't hot add again non-running container resources to avoid having extra
and useless resources
fixes#2186
Signed-off-by: Julio Montes <julio.montes@intel.com>
GetOCISpec returns a patched version of the original OCI spec, it was modified
to support:
* capabilities
* Ephemeral storage
* k8s empty dir
In order to avoid consusions and make api clear, rename GetOCISpec
to GetPatchedOCISpec and ContainerConfig.Spec to ContainerConfig.CustomSpec
fixes#2252
Signed-off-by: Julio Montes <julio.montes@intel.com>
When call "C" func directly, it's needed to change the string to
CString. To avoid using the unsafe calling, replace it with the
rust safe function to set mode for a file/dir.
Signed-off-by: lifupan <lifupan@gmail.com>
Currently kata-runtime saves the Container OCI Spec even when it's not needed
and a comment in `ContainerConfig struct` specifically indicates that
it won't be saved to disk.
Use '-' as json tag instead of '_' to indicates that `Spec` field shouldn't
be saved to disk.
fixes#2256
Signed-off-by: Julio Montes <julio.montes@intel.com>
BlockIndex should not increment in case of error.
Similar issue applies to decrementSandboxBlockIndex where the symptom may be more severe - in worst case, the block index may become negative.
Fixes#2244
Signed-off-by: Ted Yu <yuzhihong@gmail.com>
- vc: Remove unnecessary call to kill
- versions: Add cloud-hypervisor
- clh: fix build
- vc: Remove extra call to Kill
- FC: log out the firecracker's console when debug enabled
- Add support for intel cloud hypervisor
- Remove nemu
- fc: config: vhost-net not supported
- qemu-configs: update disable_vhost_net description
- Topic/network simplify
- support firecracker 0.19.0
- rootless: Fix cgroup creation logic for rootless
- FIPS: Add support for starting VM in FIPS mode.
- vc/qemu: add mutex to qmp monitor channel in qmpSetup()
- version: Update containerd version to 1.3.0
- rootless: Fix rangeUID parsing
- versions: Update kubernetes and cri-o to 1.16
1e04679 versions: Add cloud-hypervisor
618666e vc: Remove unnecessary call to kill
510f0a6 clh: fix build
ee9a53c vc: Remove extra call to Kill
784066a Makefile: clh: Use virtiofs kernel
01713d5 runtime: added cloud hypervisor driver
70297c2 nemu: remove nemu support
a2b6afc FC: log out the firecracker's console when debug enabled
13a00a2 virtcontainers: add a stateful to FC struct
0c482b2 qemu-configs: update disable_vhost_net description
519eff7 fc: config: vhost-net not supported
6154210 versions: bump firecracker version
78ca966 virtcontainers: bump firecracker minimum supported version
77b0dfb virtcontainers: use new firecracker API
0def9b0 virtcontainers/firecracker: update API
744ccd4 network: Set the default config to tcfilter
27433d9 config: Get rid of bridged model docs in the configuration
dffc988 virtcontainers: Eliminate legacy networking models
f6ffb79 rootless: Fix cgroup creation logic for rootless
0bd41b9 FIPS: Add support for starting VM in FIPS mode.
3f1a39c rootless: Fix rangeUID parsing
69ab092 versions: Add cri-tools and conmon to the versions.yaml
5b31282 vc/qemu: add mutex to qmp monitor channel in qmpSetup()
0e70b38 versions: Update kubernetes and cri-o to 1.16
62f64bb version: Update containerd version to 1.3.0
Signed-off-by: Archana Shinde <archana.m.shinde@intel.com>
