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

[Saint Michael]

My applications are very complex and involved many applications in the
traditional sense. It is a nightmare to install them.
My application runs on Centos but I prefer to use Ubuntu as LXC host.
I found that rsynching a container over the WAN is the only perfect way to
deploy.
The issue that kills me is why I can change some kernel parameters, but not
for example
net.core.rmem_max = 67108864
net.core.wmem_max = 33554432
net.core.rmem_default = 31457280
net.core.wmem_default = 31457280
Any idea?





On Mon, May 27, 2019 at 2:57 AM Jäkel, Guido <G.Jaekel at dnb.de> wrote:

> Dear Michael,
>
>         > For me, the single point of using LXC is to be able to redeploy
> a complex
>         > app from host to host in a few minutes. I use
> one-host->one-Container. So
>         > what is the issue of giving all power to the containers?
>
> I don't understand yet, why you want to use Containers, LXC or Dockers at
> all: You need to have full access to the host and it hardware at low level
> and don't want to use any isolation or virtualization aspects at all. If
> you just want to redeploy a complex setup within minutes, you may just need
> to use a prepared backup of your hosts, or an layered setup with an
> read-only image and an writeable layer for the changes.
>
> Guido
>
> _______________________________________________
> 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/20190527/fc628326/attachment.html>