mirror of
https://github.com/kata-containers/kata-containers.git
synced 2026-07-14 13:29:19 +00:00
aa7e46b5ed
One problem that we've been having for a reasonable amount of time, is containerd not behaving very well when we have multiple snapshotters. Although I'm adding this test with my "CoCo" hat in mind, the issue can happen easily with any other case that requires a different snapshotter (such as, for instance, firecracker + devmapper). With this in mind, let's do some stability tests, checking every hour a simple case of running a few pre-defined containers with runc, and then running the same containers with kata. This should be enough to put us in the situation where containerd gets confused about which snapshotter owns the image layers, and break on us (or not break and show us that this has been solved ...). Signed-off-by: Fabiano Fidêncio <ffidencio@nvidia.com>
33 lines
704 B
YAML
33 lines
704 B
YAML
# Copyright (c) 2024 Red Hat
|
|
#
|
|
# SPDX-License-Identifier: Apache-2.0
|
|
#
|
|
# Configuration file with rules for the actionlint tool.
|
|
#
|
|
self-hosted-runner:
|
|
# Labels of self-hosted runner that linter should ignore
|
|
labels:
|
|
- amd64-nvidia-a100
|
|
- arm64-k8s
|
|
- containerd-v1.7
|
|
- containerd-v2.0
|
|
- containerd-v2.1
|
|
- containerd-v2.2
|
|
- garm-ubuntu-2004
|
|
- garm-ubuntu-2004-smaller
|
|
- garm-ubuntu-2204
|
|
- garm-ubuntu-2304
|
|
- garm-ubuntu-2304-smaller
|
|
- garm-ubuntu-2204-smaller
|
|
- k8s-ppc64le
|
|
- ubuntu-24.04-ppc64le
|
|
- metrics
|
|
- ppc64le
|
|
- riscv-builder
|
|
- sev-snp
|
|
- s390x
|
|
- s390x-large
|
|
- tdx
|
|
- ubuntu-22.04-arm
|
|
- ubuntu-24.04-s390x
|