Conmon warnings every 30s for memory.events with rootless podman container

[andreasjarliden]

I run a rootless podman container on OpenSUSE MicroOS. The container is working fine although I get the following warning every 30s when conmon tries to check the memory.events file for the container

conmon 6d47ba2f69f3682e855c <nwarn>: Failed to add inotify watch for /sys/fs/cgroup/user.slice/user-1000.slice/user@1000.service/user.slice/user-libpod_pod_....slice/libpod-....scope/memory.events

The folder exists, but not the memory.events file. I suspect this is because
/sys/fs/cgroup/user.slice/cgroup.subtree_control (and below) only contains pids but not memory like /sys/fs/cgroup/cgroup.subtree_control does.

I don’t think that I do anything special when launching the container, so I’m surprised that I get these warnings. Is it correct that conmon assumes memory to be enabled for user.slice? Is it MicroOS that is unusual in this?

[jnovy]

Assuming we need a check if memory.events file exists before attempting to add inotify watch. When running rootless containers where the memory controller is not enabled in the user slice, the file doesn't exist and the inotify_add_watch() would fail with a warning every time.