-
# Get your issue reviewed faster
Hi there
# Description of problem
My underlying h/w didn't change but, starting with snap v710 (used to solve #1122), initial kata-containers.runtime check says…
-
# Description of problem
Running:
- Kata Runtime 1.6.0rc2 (RPM's for 1.6.0rc1 with just the runtime updated since they weren't available at the time of this test)
- Kubernetes 1.13.3
- CRIO 1.13…
-
Using the rust agent 2.0, we have a lot of failures on the CRI-O tests
```
10:39:04 not ok 2 ctr termination reason Completed
10:39:04 # (in test file ctr.bats, line 28)
10:39:04 # `[ "$status" …
-
# Description of problem
docker-compose up stop with an error message (works without kataruntime)
# Expected result
All dockers image runs
# Actual result
ERROR: for app_apache-rp_1…
-
# Description of problem
Set default_memory = 16384
Kata runtime failed to create:
runtime log:
msg="Unable to hotplug 16384 MiB memory, the SB has 116736 MiB and the maximum amount is 2048 MiB"…
-
# Description of problem
The image started by systemd cannot be run. Will report an error
> v1 docker run --runtime kata-runtime --name kata-test --cpus 2 --memory 2G -itd crawler:v2
1c057dc5…
-
# Description of problem
Similar to #1279, we need to be able to keep guest time synchronized. Using ptp_kvm for a virtual PHC seems like an appropriate solution.
# Expected result
According …
-
# Description of problem
1. Enable host OS binder driver and ashmem then launch android image by runc successfully;
2. Rebuild kata guest kernel and add two android depending on modelers: bind…
-
use osbuilder to build rust agent.
-