Rophy Tsai

> Comment for the commit message, please fix https://github.com/kata-containers/kata-containers/actions/runs/15373183943/job/43258719571?pr=11353 accordingly 😉 Fixed

I managed to upgrade nodejs to 18, fix critical CVEs by manaually, minimally force upgrade some packages, and rewrite Dockerfile to not rely on the ancient published npm package: https://github.com/audreyt/ethercalc/compare/master...rophy:ethercalc:fix-critical-cve...

> Adding below lines in `/etc/containerd/config.toml` solved the problem for me. > > ``` > [plugins."io.containerd.grpc.v1.cri".containerd] > snapshotter = "devmapper" > ``` This is for containerd. I am having the...

from minikube node: ```bash bash-5.2# find /run/kata-containers/shared/ /run/kata-containers/shared/ /run/kata-containers/shared/sandboxes /run/kata-containers/shared/sandboxes/3bc43dd80f3d933470ddf6ea21f00c57f909953a5cb1840ab5556058eeae518d /run/kata-containers/shared/sandboxes/3bc43dd80f3d933470ddf6ea21f00c57f909953a5cb1840ab5556058eeae518d/private /run/kata-containers/shared/sandboxes/3bc43dd80f3d933470ddf6ea21f00c57f909953a5cb1840ab5556058eeae518d/private/46bac6a3284f14969f8179d2fb926b6ea9e821c40d03804106c34e72e3918cef-78f3e22f178b5184-serviceaccount /run/kata-containers/shared/sandboxes/3bc43dd80f3d933470ddf6ea21f00c57f909953a5cb1840ab5556058eeae518d/private/3bc43dd80f3d933470ddf6ea21f00c57f909953a5cb1840ab5556058eeae518d-5aea1846f390064e-hostname /run/kata-containers/shared/sandboxes/3bc43dd80f3d933470ddf6ea21f00c57f909953a5cb1840ab5556058eeae518d/private/3bc43dd80f3d933470ddf6ea21f00c57f909953a5cb1840ab5556058eeae518d-e0d3eed57f845ed8-resolv.conf /run/kata-containers/shared/sandboxes/3bc43dd80f3d933470ddf6ea21f00c57f909953a5cb1840ab5556058eeae518d/mounts /run/kata-containers/shared/sandboxes/3bc43dd80f3d933470ddf6ea21f00c57f909953a5cb1840ab5556058eeae518d/mounts/3bc43dd80f3d933470ddf6ea21f00c57f909953a5cb1840ab5556058eeae518d-5aea1846f390064e-hostname /run/kata-containers/shared/sandboxes/3bc43dd80f3d933470ddf6ea21f00c57f909953a5cb1840ab5556058eeae518d/mounts/3bc43dd80f3d933470ddf6ea21f00c57f909953a5cb1840ab5556058eeae518d-e0d3eed57f845ed8-resolv.conf /run/kata-containers/shared/sandboxes/3bc43dd80f3d933470ddf6ea21f00c57f909953a5cb1840ab5556058eeae518d/mounts/3bc43dd80f3d933470ddf6ea21f00c57f909953a5cb1840ab5556058eeae518d /run/kata-containers/shared/sandboxes/3bc43dd80f3d933470ddf6ea21f00c57f909953a5cb1840ab5556058eeae518d/mounts/3bc43dd80f3d933470ddf6ea21f00c57f909953a5cb1840ab5556058eeae518d/rootfs /run/kata-containers/shared/sandboxes/3bc43dd80f3d933470ddf6ea21f00c57f909953a5cb1840ab5556058eeae518d/shared ``` from sandbox vm: ```bash # enter sandbox vm shell...

Show kata-collect-data.sh details # Meta details Running `kata-collect-data.sh` version `3.16.0 (commit 213f9ddd30612c77827b7d9619a7c2da9ca8de64)` at `2025-05-25.05:01:06.283833293+0000`. --- Runtime Runtime is `/opt/kata/bin/kata-runtime`. # `kata-env` /opt/kata/bin/kata-runtime kata-env ```toml [Kernel] Path = "/opt/kata/share/kata-containers/vmlinux-6.12.22-151" Parameters =...

In the same machine, running minikube with identical configuration EXCEPT using containerd, and issue is gone: ```bash $ minikube start --vm-driver kvm2 --memory 6144 --container-runtime=containerd --kubernetes-version=1.31.9 $ git clone https://github.com/kata-containers/kata-containers.git...

It seems the issue is narrowed down to specifically cri-o. My environment needs to use cri-o, so any hints would be appreciated.

I have successfully run kata-containers + cri-o with kvm and microk8s, and I hope I have nailed down the root cause of this issue. Issue 1: kata-containers with cri-o requires...

Tested OK for me for (a) local oidc-server-mock and (b) auth0. Note that the first time you run `docker-compose up`, kutt crashes trying to discover OIDC endpoints while oidc-server-mock is...

rophy/kutt [main](https://github.com/rophy/kutt/tree/main) branch now points to rophy/oidc branch + auto build. docker build for testing: https://github.com/rophy/kutt/pkgs/container/kutt/main