Search results

Is this still the case?

@fabian did you manage to have a look? thanks

Did you find anything? I'd like to use ClusterAPI but instead of having nodes as QEMU VMs, it would be nice if the nodes could be LXC containers. Now, I don't know if kubernetes is supposed to run in LXC containers, but still :)

Yeah, it took a while to get it accepted. I should have subscribed to the list as mentioned here in the forum... Anyways, thanks for checking! Let me know if I should send the patch upstream instead.

@fabian any chance this gets reviewed and/or integrated?

The patch went in to the lists but so far no reply: https://lists.proxmox.com/pipermail/pve-devel/2024-May/064114.html

I've sent a patch to the lists, still waiting for approval to be posted. Subject: [PATCH lxcfs 0/1] d/rules: Allow passing options to the lxcfs systemd unit Reason: Post by non-member to a members-only list Dunno if it's a valid solution since it lacks validations. I did some basic testing in...

Indeed, not yet sent. Will report when I do it :)

Actually I think I'll send a patch but I have no clue if it'll be accepted.

In the bugzilla issue they didn't fix anything, just closed it and provided a workaround, which in my view is not optimal. Not sure where the change should go, but there should be a /etc/default/lxcfs with a LXCFS_OPTS= var to able to specify whether you want this enabled or not. I understand...

Can't you just use a vswitch then? https://docs.hetzner.com/robot/dedicated-server/network/vswitch/

Yeah, I'm doing something similar right now, I might share my setup too!

What are those blue.de compute nodes for 1eur a month?

Any news?

Thanks @fabian, I've read the corosync github issue, looked quited involved :) Good job!

Is there a solution for this? If you're using ZFS and with aufs gone, your only choice seems to use fuse-overlayfs but then you can't backup the LXC or use ZFS replication, can you even migrate LXCs?

Same here: Version: root@pve02:~# pveversion pve-manager/6.3-6/2184247e (running kernel: 5.4.106-1-pve)

Hi all, We eventually found what was causing the leak and it was not in proxmox. It was a bug in a library (nss-softokn) in the Centos7 CTs, which is fixed by upgrading that library to a newer version, see the relevant commit: Bug 1603801 [patch] Avoid dcache pollution from sdb_measureAccess()...

The journal size is pretty small tbh: root@pmxc-12:~# journalctl --disk-usage Archived and active journals take up 24.0M in the file system. By the way, the OOM killer is never triggered because the CT gets almost up to its mem limit. 97% or so.

Thanks @oguz, if you need any more information let me know. I'll keep investigating on my side but at this point I'm out of ideas.