-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rhel7 k3s start not working with containerd - failed to find snapshotter overlayfs #495
Comments
Is the overlay kernel module available? (output for |
Yes k3s service is running. Here is the status
|
Here is the detail of the log when I start as #./k3s server
|
Because of SELinux? |
No SELinux:
|
I was able to make some progress with docker though.
But, needed to start the docker native.cgroupdriver with cgroupfs instead of systemd:
However, my intention is to use the containerd instead of docker. I still assume there is some issue with the spawned contained running from k3s. Here is the details k3s stdout and the corresponding containerd.log:
/var/lib/rancher/k3s/agent/containerd/containerd.log
|
AFAICT this is caused by
|
I had this issue and I solved it by using a xfs filesystem created with:
Some details here: https://docs.docker.com/storage/storagedriver/overlayfs-driver/ |
Thanks a bunch @aucampia . That is the the issue. Later versions of RHEL7 mkfs the new filesystem with default fstype=1. However, I was using the old rhel7 version from template where /var was already formatted. Had to create a new xfs filesystem /var/lib/rancher where the new ftype setting is automatically formatted with fstype 1, and there is no longer overlayfs issue with containerd. My coredns and traefik pods and now running :) |
Thanks , it solved my problem also. I'm running K3S on a Oracle Linux Server release 7.5 VM and now it is functioning with containerd. |
I was also eaten by this trying to run on a much older file-system |
Closing due to age |
I am trying to start k3s in rhel7. The service starts fine but no pods get deployed. Looks like some issues in containerd as shown in the log.
I suspect this warning in containerd is causing the issue:
failed to create CRI service: failed to find snapshotter "overlayfs"
System: rhel7.6
Trying to install k3s in air gap mode.
File contents:
The last line repeats indefinitely.
containerd.log:
Note:
The text was updated successfully, but these errors were encountered: