On Sun, May 08, 2016 at 07:53:22PM +0000, drkh5h on Github wrote: > +# fixes for systemd in lxc container > +ln -s /dev/null /etc/systemd/system/systemd-udevd.service > +ln -s /dev/null /etc/systemd/system/systemd-udevd-control.socket > +ln -s /dev/null /etc/systemd/system/systemd-udevd-kernel.socket > +ln -s /dev/null /etc/systemd/system/proc-sys-fs-binfmt_misc.automount
None of this is needed because systemd doesn't start those units in a container [1]. I have checked this with arch and fedora 22 containers. [1] https://lists.freedesktop.org/archives/systemd-devel/2016-February/035726.html Sincerely, L. -- Leonid Isaev GPG fingerprints: DA92 034D B4A8 EC51 7EA6 20DF 9291 EE8A 043C B8C4 C0DF 20D0 C075 C3F1 E1BE 775A A7AE F6CB 164B 5A6D _______________________________________________ lxc-devel mailing list lxc-devel@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-devel
