Bug#917122: systemd can not start without name_to_handle_at option

2018-12-23 Thread Michael Biebl
On Sun, 23 Dec 2018 00:15:55 + Vladimir Tiukhtin wrote: > Hi > > I believe it can be found here https://github.com/systemd/systemd/pull/5499 Ok, thanks for the reference. I've updated the bug meta-data accordingly. Have you verified that the patch fixes your problem with docker? If so,

Bug#917122: systemd can not start without name_to_handle_at option

2018-12-22 Thread Vladimir Tiukhtin
Hi I believe it can be found here https://github.com/systemd/systemd/pull/5499 On Sat, 22 Dec 2018 at 23:47, Michael Biebl wrote: > Control: tags -1 + moreinfo > > Am 23.12.18 um 00:29 schrieb Vladimir Tiukhtin: > > Docker limits this system call be default. However RedHat image is > > running

Bug#917122: systemd can not start without name_to_handle_at option

2018-12-22 Thread Michael Biebl
Control: tags -1 + moreinfo Am 23.12.18 um 00:29 schrieb Vladimir Tiukhtin: > Docker limits this system call be default. However RedHat image is > running correctly which means that they have back ported a patch for > systemd from upstream which resolves this problem on systemd side. Can > you

Bug#917122: systemd can not start without name_to_handle_at option

2018-12-22 Thread Vladimir Tiukhtin
Package: systemd Version: 232-25+deb9u6 Running Debian Stretch in docker container results in Failed to determine whether /sys is a mount point: Operation not permitted Failed to determine whether /proc is a mount point: Operation not permitted Failed to determine whether /dev is a mount point: