Closed nishantmunjal7 closed 2 months ago
Are you sure you mirrored the images properly? What are you using as the image snapshotter? The message from containerd indicates that content (specifically the entry point executable) is missing from the images.
Yes, as per the logs
We are putting the airgapped images tar inside ~/.rancher/k3s/agent/images/
I0828 16:21:51.115381 54 garbagecollector.go:157] "All resource monitors have synced. Proceeding to collect garbage" logger="garbage-collector-controller"
time="2024-08-28T16:21:52Z" level=info msg="Imported docker.io/rancher/klipper-helm:v0.8.4-build20240523"
time="2024-08-28T16:21:52Z" level=info msg="Imported docker.io/rancher/klipper-lb:v0.4.9"
time="2024-08-28T16:21:52Z" level=info msg="Imported docker.io/rancher/local-path-provisioner:v0.0.28"
time="2024-08-28T16:21:52Z" level=info msg="Imported docker.io/rancher/mirrored-coredns-coredns:1.10.1"
time="2024-08-28T16:21:52Z" level=info msg="Imported docker.io/rancher/mirrored-library-busybox:1.36.1"
time="2024-08-28T16:21:52Z" level=info msg="Imported docker.io/rancher/mirrored-library-traefik:2.10.7"
time="2024-08-28T16:21:52Z" level=info msg="Imported docker.io/rancher/mirrored-metrics-server:v0.7.0"
time="2024-08-28T16:21:52Z" level=info msg="Imported docker.io/rancher/mirrored-pause:3.6"
time="2024-08-28T16:21:52Z" level=info msg="Imported images from /home/atlanedit/.rancher/k3s/agent/images/k3s-airgap-images-amd64.tar.zst in 12.731775886s"
And its using fuse-overlayfs
as snapshotter
k3s crictl info
"config": {
"containerd": {
"snapshotter": "fuse-overlayfs",
"defaultRuntimeName": "runc",
"defaultRuntime": {
"runtimeType": "",
"runtimePath": "",
"runtimeEngine": "",
"PodAnnotations": null,
"ContainerAnnotations": null,
"runtimeRoot": "",
"options": null,
"privileged_without_host_devices": false,
"privileged_without_host_devices_all_devices_allowed": false,
"baseRuntimeSpec": "",
"cniConfDir": "",
"cniMaxConfNum": 0,
"snapshotter": "",
"sandboxMode": ""
}
Also, adding more context - This entire setup has run very well when we ran it on ec2 machine with a non-root user in an air-gapped system, but we are facing this with one of the deployment we are doing on a more-restrictive VM environment.
OK so what is the difference between the EC2 environment, and this one? I suspect that something is going on with the host, I am not aware of anything on the K3s side that would cause content to be lost from images.
The restricted environment has IPv6 blocked and dnsmasq enabled, but I don't think either of these is causing the issue.
I'm trying to diagnose the issue and understand more about it.
The logs show: Imported docker.io/rancher/klipper-helm:v0.8.4-build20240523
.
Could the k3s setup be pointing to this image (klipper-helm.8.4-build20240523) that might be missing content, specifically the entry point executable? If so, do you mean something on the host be modifying this image?
Additionally, are there other steps or checks that could help with debugging this issue?
did you figure out what the problem was?
We are attempting a K3s rootless installation on an airgapped system. While some pods are running as expected, others are encountering issues.
Running Pods:
Pods in CrashLoopBackOff:
Image:
Here are the logs