[lxc-users] not allowed to change kernel parameters inside container

[Saint Michael]

Thanks for the F grade.
In telecommunications, there is a special kind of software apps called
switches, which actually involve dozens of apps, scripts, etc. That kind of
complexity is only packageable in a container.
Other industries can get away with far simpler infrastructures. A switch is
responsible for the whole business and handles literally millions of
dollars in phone calls daily.



On Tue, May 28, 2019 at 8:57 AM Scott Lopez <scottjl at gmail.com> wrote:

> Wow, what a disaster of a thread.
>
> Wouldn't it be easier to learn how to properly package and distribute your
> application suite using a tool such as Ansible than to learn how to break
> LXC, deal with the quirks and figure out how to shoehorn it into doing what
> it wasn't designed to do?
>
> You get a B- for creativity and a F for implementation. I'd never allow
> this disaster in a production environment. Too many unforeseen consequences
> of the implementation, any issues that pop up are going to be a joy to
> track down. Is it the container, is it LXC, is it something else?
>
> Just because you can do something, doesn't mean you should.
>
> _______________________________________________
> lxc-users mailing list
> lxc-users at lists.linuxcontainers.org
> http://lists.linuxcontainers.org/listinfo/lxc-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxcontainers.org/pipermail/lxc-users/attachments/20190528/07a7499e/attachment.html>