da875e747 release: Kata Containers 2.5.0 05b2096c0 release: Adapt kata-deploy for 2.5.0 1b930156c build: Fix clh source build as normal user 01c889fb6 runtime: Fix DisableSelinux config 59bd5c2e0 container: kill all of the processes in this container 22c005f55 nydus: upgrade nydus/n...
Description of problem When trying to run a pod using the configured kata-qemu runtime class, the qemu container doesn't start or seems to stop almost immediately. Expected result ✨ magical containers running in VMs ✨ Actual result The k...
Trying deployments with increasing numbers of pods, I came across one scenario where Kata cannot utilize more than half the memory available in the cluster, whereasrunccan take advantage of a much larger fraction. Workload The workload is aspecial simple workloadintended to consume a configurable ...
5. 安装 Kata 环境 此处我们使用cloud hypervisor作为默认的 hypervisor,更多选择见kata-deploy。 git clone https://github.com/kata-containers/kata-containers.gitcdkata-containers/tools/packaging/kata-deploy/ kubectl apply -f kata-rbac/base/kata-rbac.yaml kubectl apply -k kata-deploy/overlays/k3s kubec...
[root@containerd ~]#nerdctl NAME: nerdctl - Docker-compatible CLI for containerd USAGE: nerdctl [global options] command [command options] [arguments...] VERSION: 0.12.1 COMMANDS: run Run a command in a new container exec Run a command in a running container ps List containers logs Fetch ...
{ "Bridge": "", "SandboxID": "1f15e59ae26be28242d21cfeaae218812ee77c6d23ae9c7a6dd7eb4d5222fa47", "HairpinMode": false, "LinkLocalIPv6Address": "", "LinkLocalIPv6PrefixLen": 0, "Ports": {}, "SandboxKey": "/var/run/docker/netns/1f15e59ae26b", "SecondaryIPAddresses": null,...
(null) ; status=0/0 } Slice=system.slice ControlGroup=/system.slice/docker.service MemoryCurrent=40796160 CPUUsageNSec=[not set] EffectiveCPUs= EffectiveMemoryNodes= TasksCurrent=38 IPIngressBytes=[no data] IPIngressPackets=[no data] IPEgressBytes=[no data] IPEgressPackets=[no data] IORead...
Kata version: 1.7.0-alpha0 Not sure if it's big problem, since I haven't met failures. But the guest kernel dmesg says: # dmesg -l err [ 0.762826] systemd[1]: System cannot boot: Missing /etc/machine-id and /etc is mounted read-only. [ 0...
error: unpacking of archive failed on file /usr/bin/newgidmap;5e864da7: cpio: cap_set_file error: shadow-utils-2:4.6-17.fc31.x86_64: install failed So, same root cause askata-containers/tests#2358. Maybe it's better to re-open that one as we already have some debug info there....