Exact, in the context that you are using system container as intended and supported, altering the kernel makes little sense, but that is not what I am doing here.
As I have indicated, I am intending to use the container as a way to run an OS in it that will totally control the kernel, leaving the host as actually more like a system container itself in which it won't play with the kernel. This certainly falls in the unsupported use of system containers yet at the same time so far the issue I am hitting seems to have configuration items related to them that I can play with and get to my liking as long as I understand them and adjust those to the proper value. Basically I am using a hammer to nail a screw and it may look strange from an outsider views but it makes sense from my viewpoint given my requirements. -- Yannick Koehler ________________________________ From: lxc-users <lxc-users-boun...@lists.linuxcontainers.org> on behalf of Andrey Repin <anrdae...@yandex.ru> Sent: June 15, 2020 10:51 AM To: Saint Michael <lxc-users@lists.linuxcontainers.org>; All <lxc-users@lists.linuxcontainers.org> Subject: Re: [lxc-users] Running unprotected system container Greetings, Saint Michael! > I need to load kernel modules, etc. It has to be on equal footing with the > host > .. See my other reply to the thread. "I need to load kernel modules" is a direct contradiction to kernel-agnostic premise of containers. -- With best regards, Andrey Repin Monday, June 15, 2020 17:50:09 Sorry for my terrible english... _______________________________________________ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
_______________________________________________ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
