to:
http://www.freedesktop.org/wiki/Software/systemd/ContainerInterface/
"Container managers should stay away from the "name=systemd" cgroup
hierarchy. That's private property of systemd, and no other code should
interfere with it. "
Regards.
--
Dariusz Michaluk
Samsung R&
Hi.
Another week, another experiment ;) I was trying to run systemd user
session for non-root user, for example darek (uid=1000), operation
failed with error:
systemd[26]: pam_unix(systemd-user:session): session opened for user
darek by (uid=0)
systemd[1]: Started Login Service.
systemd[26]
On 27.02.2014 16:32, Stephan Sachse wrote:
On Thu, Feb 27, 2014 at 3:07 PM, Dariusz Michaluk
wrote:
On 26.02.2014 17:59, Stephan Sachse wrote:
# chown -R foo:foo /var/lib/libvirt/filesystems/mycontainer
you must "shift" the uids for the container 0 -> 666, 1 -> 667, 2 -&
information ;)
--
Dariusz Michaluk
Samsung R&D Institute Poland
Samsung Electronics
d.micha...@samsung.com
___
libvirt-users mailing list
libvirt-users@redhat.com
https://www.redhat.com/mailman/listinfo/libvirt-users
tted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 0.066/0.071/0.077/0.010 ms
Yes you are right, chown removed capabilities, but ping still works
properly.
--
Dariusz Michaluk
Samsung R&D Institute Poland
Samsung Electronics
532344]
pid -> pid:[4026532342]
user -> user:[4026532337]
uts -> uts:[4026532339]
outside container
$ ls -l /proc/self/ns/
ipc -> ipc:[4026531839]
mnt -> mnt:[4026531840]
net -> net:[4026531956]
pid -> pid:[4026531836]
u
