Recent content by tabnul

I tried , it worked (cluster worked) but i recerted to vms. - too much permissions needed, basically giving full host access to k8s - issues with snapshotter in combination with zfs backed storage - endlessly eating storage space for no reason - i was expecting issues with longhorn, as...

Thank you for your reply. This indeed fixes it. I do think the example code as referenced in the docs should be updated then; https://git.proxmox.com/?p=pve-manager.git;a=blob;f=vzdump-hook-script.pl;h=a93eeec80bd09128e70a4a9775438ab658da2191;hb=refs/heads/master

It seems that the TARFILE variable isnt available anoymore for backup hooks in proxmox 7.1 I tested it and it is not available in backup-start, backup-end and log-end stages. Seems a bug to me. See also this PR where i implemented a workaround for a script that worked for 6.*...

In the logs you should find a line that states that these modules are loaded.

K3S explicitly modprobes those modules and that fails. However they are actually loaded and it uses hem regarless. Same behavior with microk8s. So consider those messages 'informal'.

would tweaking apparmor make it work for k3s? i see microk8s delivers apparmor profiles as part of their solution; https://github.com/ubuntu/microk8s/issues/1214

When using fuse-overlay with ZFS, backupping or replicating the container results in a hard freeze of the container. I solved that by using the 'native' snapshotter. But it seems the native snapshotter is not recommended for production workloads -- slowly i am leaning more and more towards vm's...

great thanks, was allready looking at that thread. i dislike the fact that apparmor needs to be disabled to get it working. i am going to upgrade regardless , might revert to VM's for k3s.

have you tried the ' native ' snapshotter? works here with k3s/containerd and i can replicate my zfs hosted lxc container. by the way i can confirm your issue, container frozen after testing with fuse-overlayfs and setting up a replication...

I followed the same guide and it works. My K3s does however throw those errors as well, seems to be false positive. proxmox 6.4 latest, ubuntu 20.04 lxc, latest k3s stable

Same issue (modprobe errors, not the cpu errors) here however k3s is running actually, 3 node cluster with core services up and running. Seems that the errors can be ignored if you actually have those modules loaded. by the way i followed this guide, ignoring the first command...

I am wondering, anyone found a solution? I have the same issue here, ubuntu 20.0.4 LXC on proxmox 6.4 latest. Followed the guide linked above. K3S start: error on both overlay and br_netfilter K3S seems to be working allright though, i have a 3 node cluster running and core pods are running...

I didnt have this issue on ubuntu 18.0.4 , using legacy installer. However I can confirm this issue for ubuntu 20.0.4, using subiquity installer. Had huge problems using an image that was generated by packer. Basically none of the cloud-init logic was applied after using the image, the...

candidate here as well ;) Would be a good feature for added flexibility.

Fixed it by creating a ZFS volume manually on the cluster level. After moving the VM disks to that location i can replicate them.