Closed xiaogr closed 3 years ago
anyone has comment? :-S
cc @likebreath
@xiaogr Excuse for the delayed response. In case you missed it, Kata 1.11.3
is a stable release to older versions, while the 1.12.0-alpha1
is the latest release.
I would advise you to setup the latest release of kata w/ kata-deply
. The kata-deploy README should be self-explainable. Note that the latest runtimeClass.yaml w/ k8s-1.18 is here where it covers kata-qemu
, kata-qemu-virtiofs
, kata-fc
and kata-clh
. Hope it helps. Any further questions, please just ask.
We recommend moving to 1.12.1 (or the latest release :-)) and closing it for now (please reopen if needed).
Hi,
I was trying to use clh as kata's hypervisor, however, the sandbox failed to start. After some rough debug, i noticed it failed at:
func (clh *cloudHypervisor) bootVM(ctx context.Context) error {
the clh api server responded with: ID=fd26505c2b563c6ae8a2c351799cc510ba27b9e08067af945dc8b477a6689346 error="error: 400 reason: SerdeJsonDeserialize(Error(\"missing field
sock
\", line: 1, column: 845))" source=virtcontainers subsystem=cloudHypervisorBTW, there is a BUG that no cleanup work if that error condition happened, that caused new vm was created infinitely and failed VMs were still staying on the system.
Could anyone figure out anything was wrong?
Get your issue reviewed faster
To help us understand the problem more quickly, please do the following:
kata-collect-data.sh
script, which is installed as part of Kata Containers.Show kata-collect-data.sh details
Meta details
Running
kata-collect-data.sh
version1.12.0-alpha1 (commit 2be92dd721363a9d204bb67b3276dde596b7d090)
at2020-10-12.21:59:29.349049839+0800
.Runtime is
/bin/kata-runtime
.kata-env
Output of "
/bin/kata-runtime kata-env
":Runtime config files
Runtime default config files
Runtime config file contents
Output of "
cat "/etc/kata-containers/configuration.toml"
":Config file
/usr/share/defaults/kata-containers/configuration.toml
not foundKSM throttler
version
Output of "
--version
":systemd service
Image details
Initrd details
No initrd
Logfiles
Runtime logs
No recent runtime problems found in system journal.
Proxy logs
No recent proxy problems found in system journal.
Shim logs
No recent shim problems found in system journal.
Throttler logs
No recent throttler problems found in system journal.
Container manager details
Have
docker
Docker
Output of "
docker version
":Output of "
docker info
":Output of "
systemctl show docker
":Have
kubectl
Kubernetes
Output of "
kubectl version
":Output of "
kubectl config view
":Output of "
systemctl show kubelet
":No
crio
Havecontainerd
containerd
Output of "
containerd --version
":Output of "
systemctl show containerd
":Output of "
cat /etc/containerd/config.toml
":Packages
No
dpkg
Haverpm
Output of "rpm -qa|egrep "(cc-oci-runtimecc-runtimerunv|kata-proxy|kata-runtime|kata-shim|kata-ksm-throttler|kata-containers-image|linux-container|qemu-)"
":Description of problem
$ cat clh-runtimeclass.yaml kind: RuntimeClass apiVersion: node.k8s.io/v1beta1 metadata: name: clh handler: clh
$ cat clh-vcont-host2.yaml apiVersion: v1 kind: Pod metadata: name: clh-vcont-host2 labels: run: vcont spec: restartPolicy: Never runtimeClassName: clh containers:
kubectl create -f ./clh-runtimeclass.yaml
kubectl create -f ./clh-vcont-host2.yaml
kubectl get pods
NAME READY STATUS RESTARTS AGE clh-vcont-host2 0/1 ContainerCreating 0 16h
Expected result
pod should be created successfully
Actual result
it failed
Further information
qemu and fc hypervisos both worked well.