Channels
academy
amazon
arm
azure
cabpr
chinese
ci-cd
danish
deutsch
developer
elemental
epinio
espanol
events
extensions
fleet
français
gcp
general
harvester
harvester-dev
hobbyfarm
hypper
japanese
k3d
k3os
k3s
k3s-contributor
kim
kubernetes
kubewarden
lima
logging
longhorn-dev
longhorn-storage
masterclass
mesos
mexico
nederlands
neuvector-security
office-hours
one-point-x
onlinemeetup
onlinetraining
opni
os
ozt
phillydotnet
portugues
rancher-desktop
rancher-extensions
rancher-setup
rancher-wrangler
random
rfed_ara
rio
rke
rke2
russian
s3gw
service-mesh
storage
submariner
supermicro-sixsq
swarm
terraform-controller
terraform-provider-rancher2
terraform-provider-rke
theranchcast
training-0110
training-0124
training-0131
training-0207
training-0214
training-1220
ukranian
v16-v21-migration
vsphere
windows
Powered by
Title
l
late-needle-80860
01/27/2023, 1:04 PM
Question on customizing containerd. I’ve read: •
https://docs.k3s.io/advanced#configuring-containerd
and •
https://github.com/k3s-io/k3s/blob/master/pkg/agent/templates/templates_linux.go
Is that approach the recommended way of doing things in regards to customizing root = "/var/lib/containerd" and state = "/run/containerd" As mentioned in:
https://github.com/containerd/containerd/blob/main/docs/ops.md#base-configuration
??? —- The goal is to have container images and other non runtime related containerd data on a non system disk to avoid disk space usages on system disks. Thank you
Anyone? Fellow K3s connoisseurs 😄
#k3s
Join Slack