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

[Saint Michael]

The Achilles' heel is the type of CPU. I had to recompile my app once I
moved it to an older CPU. Nothing is portable 100%.
I guess nothing allows you to get rid of the developer at the end of the
day.

On Tue, May 28, 2019 at 9:25 PM Fajar A. Nugraha <list at fajar.net> wrote:

> On Tue, May 28, 2019 at 8:18 PM Saint Michael <venefax at gmail.com> wrote:
>
>> 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.
>>
>
> It's a matter of choice. AT&T seems to go with VMs and openstack:
> https://www.theregister.co.uk/2016/01/08/att_expanding_sdn/
>
> That being said, https://anbox.io/ does something similar with you: they
> package complex apps using lxc. In their case, they use snaps for
> distribution, and then use lxc internally.
>
> --
> Fajar
>
> _______________________________________________
> 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/8b832db8/attachment.html>