On 12/31/2017 07:19 PM, Michael Biebl wrote: > Am 30.12.2017 um 14:27 schrieb Alex Mestiashvili: >> On 12/30/2017 01:46 PM, Michael Biebl wrote: >>> Am 30.12.2017 um 13:02 schrieb Alex Mestiashvili: >>> >>>> There are some cases when using sysvinit is preferred over systemd. >>>> AFAIK there is no way drop some capabilities with systemd geared linux >>>> containers while it is possible with sysvinit. >>> >>> It's the first time I hear about this. Can you please elaborate? I'd >>> like to know more about this. >> >> Last time I run into this issue was more than two years ago. See this >> link [0]. Quick googling now brought me to this discussion[0]. The issue >> seem to be fixed now, so I guess I'll give it another try. > > Ok, so this is/was outdated information. Thanks for the confirmation. >
Not really. More precisely I don't know what is the status now. What I have observed a number of times within the last 2 years is that linux containers with systemd where not working for my needs. The solution was two switch to sysvinit and forget about the problem. According to this [0] the issue might be fixed but I have not tested it so far. In any case I think it is important to keep sysvinit scripts unless there is a good reason not to. [0] https://github.com/lxc/lxc/issues/1737
