d/rules: enable CONFIG_MEMCG_V1 needed for legacy containers

As reported in the community forum [0], containers requiring cgroup v1
would not start anymore, even when systemd.unified_cgroup_hierarchy=0
was set on the kernel commandline. The error message would be:

> cgfsng_setup_limits_legacy: 3442 No such file or directory - Failed to set "memory.limit_in_bytes" to "536870912"

Kernel commit e93d4166b40a ("mm: memcg: put cgroup v1-specific code
under a config option"), which was first shipped in v6.11, made it
necessary to explicitly enable the new associated Kconfig flag.

[0]: https://forum.proxmox.com/threads/156830/

Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
 [TL: note that the commit was first shipped with 6.11 ]
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
This commit is contained in:
Fiona Ebner 2024-11-05 14:27:19 +01:00 committed by Thomas Lamprecht
parent a681faec23
commit 2519c2669d

1
debian/rules vendored
View File

@ -65,6 +65,7 @@ PMX_CONFIG_OPTS= \
-e CONFIG_MODULE_SIG_SHA512 \
-d CONFIG_MEMCG_DISABLED \
-e CONFIG_MEMCG_SWAP_ENABLED \
-e CONFIG_MEMCG_V1 \
-e CONFIG_HYPERV \
-m CONFIG_VFIO_IOMMU_TYPE1 \
-e CONFIG_VFIO_VIRQFD \