--memory parameter cannot be used due to missing cgroup feature

[p-se]

Podmans --memory parameter is used in monitoring component containers. This fails with

Your kernel does not support swap limit capabilities,or the cgroup is not mounted. Memory limited without swap.

While removing the --memory parameter off the run files works, it's tedious to do so and can be avoided by adding cgroup_enable=memory swapaccount=1 to the kernel boot parameters variable GRUB_CMDLINE_LINUX in the /etc/default/grub file, followed by calling update-bootloader and a reboot of the VM.

It may also be noteworthy that I do not have a swap file configured on my host system but sufficient memory, not sure though if that's related.

[sebastian-philipp]

https://tracker.ceph.com/issues/43802

[smithfarm]

I can't see where sesdev is running podman anywhere. It would seem that cephadm does run podman, though.

Is this really a bug in sesdev?

[p-se]

@smithfarm we decided to move upstream with this issue and add a feature to cephadm to be able to disable the creation of services with the --memory parameter.

sesdev does indeed not directly use podman, but for ses7 and octopus deployments, podman is used. The monitoring components created by cephadm contain the --memory parameter by default and I thought it might make sense to enable this feature in the VMs created by sesdev, as this feature needs to be enable as kernel parameter. But this might not be necessary anymore due to the decision to move that issue upstream.

But without enabling the kernel feature manually or having the upstream issue resolved, this is an issue for (monitoring deployments in ses7 and octopus of) sesdev, but maybe not in sesdev.

[smithfarm]

Closing as something for cephadm/ceph-salt, not sesdev, based on my understanding of #59 (comment)