On Fri, May 15, 2015, 4:22 PM Simon McVittie <<a href="mailto:simon.mcvittie@collabora.co.uk">simon.mcvittie@collabora.co.uk</a>> wrote: <blockquote>On 15/05/15 14:17, Lennart Poettering wrote: > On Fri, 15.05.15 14:07, arnaud gaboury (<a href="mailto:arnaud.gaboury@gmail.com">arnaud.gaboury@gmail.com</a>) wrote: >> Maybe a stupid question, but shall every container user start a per >> user dbus session ? > > We make not real distinction there. We intend to provide the same > execution environment to processes running in a container as to those > running on the host Yes. As a result, you would have a `dbus-daemon --session` per user inside the container, if and only if the same OS running on real hardware would have a `dbus-daemon --session` per user (the "user bus" model). </blockquote> The host is Archlinux and has dbus- daemon per user. I am the only user and most of my services are started on a per user basis. Container is Fedora with a few allowed admins. But I cant see any debus user session when they are logged. <blockquote> In practice this means you get a `dbus-daemon --session` per user if you have dbus >= 1.9.14 compiled with the --enable-user-session option, and systemd, inside the container. </blockquote> Yes systemd is managing services in Fedora 22, the container <blockquote> Similarly, kdbus systems (inside or outside a container) always get a "user bus" per user, as far as I understand it. -- Simon McVittie Collabora Ltd. <<a href="http://www.collabora.com/">http://www.collabora.com/</a>> _______________________________________________ systemd-devel mailing list <a href="mailto:systemd-devel@lists.freedesktop.org">systemd-devel@lists.freedesktop.org</a> <a href="http://lists.freedesktop.org/mailman/listinfo/systemd-devel">http://lists.freedesktop.org/mailman/listinfo/systemd-devel</a> </blockquote>