-
# Description of problem
I create a pod using the kata runtimeclass with a memory request of `32Mi`, and a limit of `64Mi`. The pod never starts, producing this error:
```
Warning FailedCrea…
-
# History
In the very early days we used to use a very aggressively optimised kernel that only provided a minimal set of features. Over time, users requested additional features.
# Now
We cur…
-
**Which feature do you think can be improved?**
While playing around with kata I had a fairly difficult time going through the documentation. Even though there's a lot of doc pages written, I perso…
-
# Description of problem
Kata has an optimization for handling physical endpoints. This occurs when:
* Kata runs a container with an attached network interface
* Kata determines (according to …
-
When running peer-pods and Kata remote hypervisor, it is most likely being deployed alongside a traditional Kata + Kubernetes setup. These tools often provide runtime security for a multi-tenant envir…
-
So I was basically doing the same thing as explained in [this guide](https://www.redhat.com/sysadmin/image-stores-podman), setting in `/etc/containers/storage.conf` to:
```
[storage.options.overlay]…
-
**Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)**
/kind bug
**Description**
I have been doing some performance testing where I needed _many_ containers, and I th…
-
The test scenario uses 8 GPU cards and the container is not created normally.
```
root@ubuntu:~# /root/bin/ctr -n k8s.io run --rm --runtime "io.containerd.kata.v2" --device /dev/vfio/55 --device /d…
-
The `integration/kubernetes/init.sh` (see [line 189](https://github.com/kata-containers/tests/blob/main/integration/kubernetes/init.sh#L189)) remove the `NoSchedule` taint of the master node so that t…
-
### Description
Until containerd 1.7 if you started a pod sandbox and a container inside that sandbox, containerd used to issue a `shim delete` command for both the sandbox and the container during c…