Closed sidneychang closed 1 month ago
Hi @sidneychang
Actually your issue was that kata will search the config files from /etc, /usr and /opt, but it first find the configuration from /usr/share/defaults/kata-containers/runtime-rs/configuration.toml, but it seemed that this config specified the kernel image as /usr/share/kata-containers/vmlinux-dragonball-experimental.container , which didn't exist. So can double you check who deployed the configuration files in /usr/share/kata-containers/ ?
@lifupan i used to build runtime-rs manually, maybe that's the reason. thanks a lot!
Issue Description:
I'm trying to run containers on my machine using Kata Containers, and I've installed it using the kata-deploy script with the latest images in k3s. After applying each Kata Containers runtimeClass, I attempted to use ctr run to start a pod.
Steps to Reproduce:
Install Kata Containers using the kata-deploy script. Apply Kata Containers runtimeClass using
Try to use ctr run to start a pod.
Problem Description:
When attempting to start a pod using ctr run, I encountered the following error:
Attempted Solutions:
I checked the /opt/kata/share/defaults/kata-containers/runtime-rs/configuration.toml file and found that it is actually a symbolic link pointing to configuration-dragonball.toml. So, I manually copied the configuration-dragonball.toml file to /etc/kata-containers/runtime-rs/configuration.toml, which resolved the problem.
Environment:
Operating System:
Kata Containers Version:
Container Runtime:
I found that in https://github.com/kata-containers/kata-containers/blob/main/src/libs/kata-types/src/config/mod.rs#L212 will get one exist path in the pathlist as config path. I dont know its problems in my machine or in the kata-deploy script?