-
1. Pods
[root@katak8s-1 calmwu]# kubectl get pod -o wide --all-namespaces
NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE NOMINATED N…
-
# Description of problem
CRI-O fails to boot sometimes when using Kata.
# Expected result
After running `systemctl restart crio`, I expected CRI-O to restart, but it's currently stuck in the…
-
# Description of problem
Hi,
I didn't find any mention of this is 'not supported' or something about 3.0.0 particulary.
Could you, please, comment on that?
Tried Fedora rpms from http://downloa…
-
# Description of problem
Firecracker is able to bootup the kata kernel with the kata bootdisk in under .5s.
However when running with Kata the same kernel and bootdisk takes 3-4s to boot.
As a …
-
# Description of problem
vsock sockets are leaked. I'm not entirely sure whether that's a kata issue or a kernel issue. Probably kernel but you are more familiar with the innards of vsocks and kvm …
-
https://exhibits.stanford.edu/shpc/catalog/qm871dx8736 This and many other items in the SHPC exhibit display a negative number in the previous-next browse above the embed viewer: this one has "-1 of 1…
-
Issues are for bugs in syzkaller itself, for everything else please contact syzkaller@googlegroups.com mailing list.
Before filing an issue please check the existing issues and the mailing list (ht…
-
Currently we have issues in the CI mainly because the docker stability test is failing. I tried it to run it in an ubuntu machine by itself and is showing me the error that is been seen in our CI.
…
-
- Which version of Lakka are you using?
Generic.i386-2.1
- What system hardware are you using?
Dell windows xp home. No upgrades, straight out of box hardware.
- What did you do?
We USB booted. I…
-
### Ⅰ. Issue Description
Using the runV runtime creates a container with no network connectivity.
### Ⅱ. Describe what happened
Installed runV and Hyperstart according to the docs. Added run…