mirror of
https://github.com/kata-containers/kata-containers.git
synced 2025-08-31 16:36:38 +00:00
ci: k8s: Bump kcli image version
When trying to deploy nydus on kcli locally we get the following failure: ``` root@sh-kata-ci1:~# kubectl get pods -n nydus-system NAMESPACE NAME READY STATUS RESTARTS AGE nydus-system nydus-snapshotter-5kdqs 0/1 CrashLoopBackOff 4 (84s ago) 7m29s ``` Digging into this I found that the nydus-snapshotter service is failing with: ``` ubuntu@kata-k8s-worker-0:~$ journalctl -u nydus-snapshotter.service -- Logs begin at Wed 2025-02-12 15:06:08 UTC, end at Wed 2025-02-12 15:20:27 UTC. -- Feb 12 15:10:39 kata-k8s-worker-0 systemd[1]: Started nydus snapshotter. Feb 12 15:10:39 kata-k8s-worker-0 containerd-nydus-grpc[6349]: /usr/local/bin/containerd-nydus-grpc: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required b> Feb 12 15:10:39 kata-k8s-worker-0 containerd-nydus-grpc[6349]: /usr/local/bin/containerd-nydus-grpc: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required b> Feb 12 15:10:39 kata-k8s-worker-0 systemd[1]: nydus-snapshotter.service: Main process exited, code=exited, status=1/FAILURE ``` I think this is because 20.04 has version: ``` ubuntu@kata-k8s-worker-0:~$ ldd --version ldd (Ubuntu GLIBC 2.31-0ubuntu9.16) 2.31 ``` so it's too old for the nydus snapshotter. Also 20.04 is EoL soon, so bumping is better. Signed-off-by: stevenhorsman <steven@uk.ibm.com>
This commit is contained in:
@@ -272,7 +272,7 @@ function create_cluster_kcli() {
|
||||
-P ctlplanes="${CLUSTER_CONTROL_NODES:-1}" \
|
||||
-P workers="${CLUSTER_WORKERS:-1}" \
|
||||
-P network="${LIBVIRT_NETWORK:-default}" \
|
||||
-P image="${CLUSTER_IMAGE:-ubuntu2004}" \
|
||||
-P image="${CLUSTER_IMAGE:-ubuntu2204}" \
|
||||
-P sdn=flannel \
|
||||
-P nfs=false \
|
||||
-P disk_size="${CLUSTER_DISK_SIZE:-20}" \
|
||||
|
Reference in New Issue
Block a user