-
# Kata does not support block based containerd snapshotters
Kata does not support block based containerd snapshotters. This is due to an incorrect assumption in Kata that there will be a directory …
-
# Summary
I have done a some compatibility tests for kata 9pfs and I think we should change 9pfs mount option from default `cache=none` to `cache=mmap`. It does not give worse POSIX compliance (com…
-
# Description of problem
When I using k8s to bootup tomcat service, the container start failed. the container status is "CrashLoopBackOff".
the following is pod yaml file.
apiVersion:apps/v1
k…
-
# Description of problem
We are occasionally seeing failures when mounting devicemapper block devices for the container rootfs.
The following error is displayed:
```
Aug 12 02:34:07 ip-10-1…
-
```
ostree-2018.8.7-e4e6d85ea4e778c61b8f9a0301153dd0ee00b9b6.5bb0359caf4facc535ee3ee8b5ec7c552637c28d.fc28.x86_64
```
- If I pull local from bare-user (local ext2) to archive repo (local ext2) …
-
# Description of problem
We've noticed when using Containerd + devicemapper that occasionally a Kata pod is not able to be started due to a devicemapper block not being present on the host.
We h…
-
While running the soak test in Debian 9, we see that some of the containers that are being launched have the `Created` status instead of `Running` which is making the `soak test` to fail.
```
$ dock…
-
# Description of problem
Part of our workload that we run in Kata containers involves watching the logs from the Kata container on the host side from within the Kata VM. We do this by mounting the …
-
**Describe the bug**
The current Keystone build does not work on Windows Subsystem for Linux upon make.
I think it is because that Windows-styled directory names contain brackets and spaces which …
-
# Description of problem
Hello! My team and I have been trying Kata and Firecracker and we noticed that Firecracker has issues when containers are closing and opening successively / aggresively.
W…
Dodan updated
5 years ago