Hi,
Well, everything is in the subject of this message, actually... ;-).
Are there any options that need to be set before others ? I did not find
anything in the lxc.container.conf manpage but I'd like to be dead sure
since we plan to modularise our container configuration files making a heavy
On Fri, Mar 10, 2017 at 11:25:40AM +0900, Tomasz Chmielewski wrote:
> On 2017-03-10 03:16, Stéphane Graber wrote:
>
> > Hmm, then it matches another such report I've seen where some of the
> > threads are reported as using a lot of CPU, yet when trying to trace
> > them you don't actually see anyt
On 2017-03-10 03:16, Stéphane Graber wrote:
Hmm, then it matches another such report I've seen where some of the
threads are reported as using a lot of CPU, yet when trying to trace
them you don't actually see anything.
Can you try to run "strace -p" on the various threads that are reported
as
On Fri, Mar 10, 2017 at 03:01:02AM +0900, Tomasz Chmielewski wrote:
> On 2017-03-10 01:52, Stéphane Graber wrote:
>
> > Do you see a flood of events if you run "lxc monitor --type=logging"?
>
> Nope, just this:
>
> # lxc monitor --type=logging
> metadata:
> context: {}
> level: dbug
> mess
On Thu, Mar 09, 2017 at 11:01:34PM +0900, Tomasz Chmielewski wrote:
> On a server with several ~idlish containers:
>
>
> PID USER PRI NI VIRT RES SHR S CPU% MEM% TIME+ Command
> 19104 root 20 0 2548M 44132 15236 S 140. 0.0 58h03:17 /usr/bin/lxd
> --group lxd --logfile=/va
Hello,
Today we're releasing security fixes for CVE-2017-5985.
This security issue was reported by Jann Horn from Google and has to do
with a lack of netns ownership check in lxc-user-nic, which would allow
any user with a lxc-usernet allocation to create network interfaces on
the host including
On a server with several ~idlish containers:
PID USER PRI NI VIRT RES SHR S CPU% MEM% TIME+ Command
19104 root 20 0 2548M 44132 15236 S 140. 0.0 58h03:17
/usr/bin/lxd --group lxd --logfile=/var/log/lxd/lxd.log
24966 root 20 0 2548M 44132 15236 S 18.2 0.0 2h45:
