You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug:
Attempting to start an RKE2 cluster on a server with limited storage. I'm keeping the installation of RKE2 on a ramdisk, but the containerd logs seems unable to launch containers. Seems related to missing CNI plugins, and possibly SELinux interference even in Permissive mode.
Steps To Reproduce:
Create RAM disk, 20 GB in storage
mkdir /tmp/rke2disk
sudo mount -t tmpfs -o size=20GB rke2disk /tmp/rke2disk
Installed RKE2 using airgapped tarball install (not using RPMs):
data-dir under ramdisk mount -t tmpfs -o size=20GB rke2disk /tmp/rke2disk
I don't think you can use overlayfs on top of tmpfs? I would ask at https://github.com/containerd/containerd if you want to be sure, but as far as I can tell this is not a problem with RKE2 - rather you are doing something that isn't supported by linux and/or containerd.
Issues with tmpfs/overlayfs aside, this could also be related to selinux - see rancher/rke2-selinux#24.
Did you mount the tmpfs volume there before installing RKE2 and the rke2-selinux RPM? How are you persisting the selinux contexts across reboots? Does tmpfs even support the required selinux xattrs?
Environmental Info:
RKE2 Version:
rke2 version v1.29.0+rke2r1 (4fd30c2)
go version go1.21.5 X:boringcrypto
Node(s) CPU architecture, OS, and Version:
4.18.0-477.10.1.el8_8.x86_64
Cluster Configuration:
1 server, storage constrained, data-dir under ramdisk
SELinux Permissive mode enabled
cgroupsv1, non-hybrid mode enabled
Describe the bug:
Attempting to start an RKE2 cluster on a server with limited storage. I'm keeping the installation of RKE2 on a ramdisk, but the containerd logs seems unable to launch containers. Seems related to missing CNI plugins, and possibly SELinux interference even in Permissive mode.
Steps To Reproduce:
Expected behavior:
Containerd starts containers sometime after loading images.
Actual behavior:
Containerd simply loads images, but seems runc fails at starting containers. Notably the following errors.
Full containerd.log
The text was updated successfully, but these errors were encountered: