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

2019-05-28 Thread Fajar A. Nugraha
On Wed, May 29, 2019 at 10:44 AM Saint Michael wrote: > 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. > If you compile it yourself,

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

2019-05-28 Thread 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 wrote: > On Tue, May 28, 2019 at 8:18 PM

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

2019-05-28 Thread Fajar A. Nugraha
On Tue, May 28, 2019 at 8:18 PM Saint Michael 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

Re: [lxc-users] unprivileged Debian Buster container on Debian Buster host fail to start: no cgroups, no controllers

2019-05-28 Thread Lukas Pirl
On Tue, 2019-05-28 21:50 +0200, Xavier Gendre wrote as excerpted: > Hello Lukas, > > unprivileged buster containers on a buster host run like a charm. Your > config includes a lot of stuff that are not suited for an unprivileged > container (apparmor, ...). First, you should try with a simpler

Re: [lxc-users] unprivileged Debian Buster container on Debian Buster host fail to start: no cgroups, no controllers

2019-05-28 Thread Xavier Gendre
Hello Lukas, unprivileged buster containers on a buster host run like a charm. Your config includes a lot of stuff that are not suited for an unprivileged container (apparmor, ...). First, you should try with a simpler configuration file as the following one. ---%<--%<--%<---

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

2019-05-28 Thread jjs - mainphrame
All the harsh criticism aside, the driving concern in business is getting it done. Many successful products have been kludges, which fulfilled a need. Jake On Tue, May 28, 2019 at 7:00 AM Scott Lopez wrote: > So? Doesn't matter if you're programming a switch or a heart monitor. > Learn how to

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

2019-05-28 Thread Scott Lopez
So? Doesn't matter if you're programming a switch or a heart monitor. Learn how to properly package your application. Apparently it was done before LXC came along, so it should still be possible today. What you want is an easy way out of simply cloning an existing installation which is never a

[lxc-users] unprivileged Debian Buster container on Debian Buster host fail to start: no cgroups, no controllers

2019-05-28 Thread Lukas Pirl
Dear all, first, thanks for the friendly and supportive help you all provide in issue trackers, on mailing lists, etc. – it is very helpful to find all this online. However, I struggle to run unprivileged (Debian Buster) containers (on a Debian Buster host). LXC does not seem to mount the cgroup

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

2019-05-28 Thread 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

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

2019-05-28 Thread Scott Lopez
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

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

2019-05-28 Thread Saint Michael
I actually think that lxc.net.0.type = none is the solution to all my problems. All I need to access my host is to use a different SSH port. I didn't know this one. Thanks to all of you. On Tue, May 28, 2019 at 1:47 AM Fajar A. Nugraha wrote: > On Tue, May 28, 2019 at 12:39 PM Saint Michael