You are not logged in.
I started with migrating from Docker to Podman on Debian, with a small amount of hurdles I got it working.
Then I followed the guide: https://www.devuan.org/os/documentation … libur.html which worked well except that I lost network and had to improvise. I might have misstepped there but I do not see what it would be.
When starting containers I get warnings:
WARN[0000] Using cgroups-v1 which is deprecated in favor of cgroups-v2 with Podman v5 and will be removed in a future version. Set environment variable `PODMAN_IGNORE_CGROUPSV1_WARNING` to hide this warning.The important containers are running well and fine but I get following in the user.log:
2026-01-08T13:31:59.485264+01:00 master conmon: conmon 2451200db3be06b80bae <nwarn>: Failed to get memory cgroup path. Container may have exitedOne interesting part is that elogind is not running (making ssh-login take 25 seconds). Trying to start elogind quietly fails.
When logging in via ssh you get:
2026-01-08T13:38:08.795011+01:00 master dbus-daemon[2543]: [system] Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms)
2026-01-08T13:38:08.795132+01:00 master sshd-session[26143]: pam_elogind(sshd:session): Failed to create session: Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms)I have a desktop system running freia where elogind starts without a problem and I can start containers without problem. It seems to find cgroup but fails with:
2026-01-08T13:53:01.166107+01:00 Big conmon: conmon 32f002b0c8f4adfaffbc <nwarn>: Failed to add inotify watch for /sys/fs/cgroup/1/memory.events
2026-01-08T13:53:01.196039+01:00 Big conmon: conmon 32f002b0c8f4adfaffbc <nwarn>: Failed to open cgroups file: /sys/fs/cgroup/1/memory.eventsNOTE: I am running as user on the desktop system and root on server.
So do I have a cgroup problem or a config problem with elogin or something else?
Offline