-
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
k3s v1.20.0+k3s2 with external containerd does not work anymore #2779
Comments
Extra info to get network with external containerd with k3s v1.19.5+k3s2 working I installed calico.yaml download calico manifest
add following to calico.yaml to get traefik working with external ip
apply calico.yaml
This is the log of a working setup of k3s (v1.19.3+k3s2) with external containerd with zfs snapshotter
|
I tracked down the cause to commit (sha1 eb72d50) of 25/11/2020 03:50:24 by @AkihiroSuda If I reverted only change in diff below then the external zfs snapshotter works again in k3s 1.20.0+k3s2
It seems that change above does not take into account when parameter --container-runtime-endpoint is used in create k3s cluster. this is the whole command I used for installing k3s
|
have you tried passing --snapshotter=zfs instead of manually altering the config template? As you noticed, the agent startup code path checks the snapshotter, but you're changing it in the template which means that k3s and containerd are out of sync. |
@brandond Thanks, that works :) FYI I checked the site documentation on --snapshotter options but was not there. But if I check k3s server --help on k3s v1.20.0+k3s2 it is there
This is the working k3s server create command
|
Yes, the documentation probably needs to be re-syncd to the current flags. |
Environmental Info:
K3s Version:
v1.20.0+k3s2
Node(s) CPU architecture, OS, and Version:
Arm64 (raspberry pi 4 8GB), Ubuntu 20.10 with zfs
Cluster Configuration:
1 master
Describe the bug:
With k3s v1.20.0+k3s2 with external containerd with zfs snapshotter does not work anywork.
With k3s v1.19.5+k3s2 it works fine
Steps To Reproduce:
install containerd
add containerd config
add config /etc/containerd/config.toml
add following
create containerd dataset
install k3s
Expected behavior:
k3s working with external containerd with zfs snapshotter
also following command should not give an error
Actual behavior:
k3s does not work with external containerd with zfs snapshotter
following command gives following error
k3s error log line related to issue
k3s complete log
The text was updated successfully, but these errors were encountered: