On 6/12/25 21:48, Михаил Иванов wrote: > Greetings! > > I'm trying to run systemd in rootless container as follows: podman > run --interactive --tty --replace --name test --systemd always > --privileged --entrypoint '[ "/usr/lib/systemd/systemd", "--system" > ]' df785493a5e5 I'm getting the following error: > >    systemd 252-46.el9_5.2.0.1 running in system mode (+PAM +AUDIT > +SELINUX -APPARMOR +IMA +SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL > +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN -IPTC +KMOD +LIBCRYPTSETUP > +LIBFDISK +PCRE2 -PWQUALITY +P11KIT -QRENCODE +TPM2 +BZIP2 +LZ4 +XZ > +ZLIB +ZSTD -BPF_FRAMEWORK +XKBCOMMON +UTMP +SYSVINIT > default-hierarchy=unified) Detected virtualization podman.    > Detected architecture x86-64.    Welcome to Rocky Linux 9.5 (Blue > Onyx)!    Failed to write /run/systemd/container, ignoring: > Permission denied    Failed to open > '/sys/firmware/dmi/entries/11-0/raw', ignoring: Permission denied    > Failed to allocate manager object: Permission denied [!!!!!!] Failed > to allocate manager object.    Exiting PID 1... > > What I'm doing wrong here? My host system is debian/testing, podman > version 5.4.2 > > Best regards, -- > Michael Ivanov > _______________________________________________ > Podman mailing list -- podman(a)lists.podman.io > To unsubscribe send an email to podman-leave(a)lists.podman.io Can you try without --privileged. You could try to run $ podman run -ti ubi9-init If this works then there is something else going on in your container images. _______________________________________________ Podman mailing list -- podman(a)lists.podman.io To unsubscribe send an email to podman-leave(a)lists.podman.io