[lxc-users] openvpn in container starts manually, but not via init script?
Simos Xenitellis
simos.lists at googlemail.com
Mon Jun 25 09:11:19 UTC 2018
Most likely it is the limitNPROC issue.
Specifically, there is a configuration option for limitNPROC to 10 in
the configuration of OpenVPN.
Normally, that should be fine because OpenVPN does not appear to
launch more than 10 processes.
However, the mere existence of the limit might be causing the issue.
See workaround on how to do that at
https://discuss.linuxcontainers.org/t/systemd-permission-problems-in-lxd-container/934
It is an issue that has been discussed at length in various bug
reports. The source of the problem
appears to be related to the code in OpenVPN that does the initialization.
Simos
On Thu, Jun 21, 2018 at 11:06 PM, Chaetoo3 <Chaetoo3 at protonmail.com> wrote:
> Oh my! I should proofread better. I got a few of P and !P backwards.
>
>> for some reason it doesn't work through openvpn's init script the way it used to in my !P container.
>
> Should be "P".
>
>> It persists even if all !P containers stop,
>
> Should be "P".
>
>
>
> _______________________________________________
> lxc-users mailing list
> lxc-users at lists.linuxcontainers.org
> http://lists.linuxcontainers.org/listinfo/lxc-users
More information about the lxc-users
mailing list