Le 2015-07-20 17:00, Serge Hallyn a écrit :
Does the failure with happen immediately after booting
the container, or after the container has actually been working
ok for awhile?
the failure happen after the container has been working ok for awhile.
You probably want to run the container a few
Hi LXC team!
Currently we limit the memory of LXC containers with:
lxc.cgroup.memory.limit_in_bytes = 92160M
lxc.cgroup.memory.memsw.limit_in_bytes = 94208M
We also monitor if the counter hits the limit via memory.memsw.failcnt.
Last week we observed that the failcnt number increased, ther
Hello,
does anybody know why my containers complain once per "lxc.mount.entry"
about "too many levels of symbolic links" and refuse to start, but
then run fine on the #mountpoints + 1st attempt?
I asked this exact question two weeks ago at stackoverflow in more
detail but got no answers. Her
On Tue, 2015-07-21 at 13:20 +0200, André Janowicz wrote:
> Hello,
>
> does anybody know why my containers complain once per
> "lxc.mount.entry" about "too many levels of symbolic links" and
> refuse to start, but then run fine on the #mountpoints + 1st
> attempt?
> I asked this exact question
Hi LXC-Users,
> is there an easy way to create/move a tap interface to an unprivileged
> container?
I think, I found a solution:
# ip tuntap add mode tap tap0
# ip link set tap0 netns 16077
This creates a tap interface with name tap0, 16077 is the PID of
the init process in the container.
On Tue, Jul 21, 2015 at 09:43:44PM +0200, Dirk Geschke wrote:
> Hi LXC-Users,
>
> > is there an easy way to create/move a tap interface to an unprivileged
> > container?
>
> I think, I found a solution:
>
># ip tuntap add mode tap tap0
># ip link set tap0 netns 16077
>
> This creates a
On Mon, Jul 20, 2015 at 3:44 PM, Mahesh Pujari
wrote:
> I had created a container with default settings and now it fails to start due
> to space issues,
What is the exact command line you use to create the container?
> how can I increase space of a container which has exhausted its space.
If b
On Monday, July 20, 2015 08:44:12 AM Mahesh Pujari wrote:
> I had created a container with default settings and now it fails to start
> due to space issues, how can I increase space of a container which has
> exhausted its space.
Most likely you have to deal with this on a lower filesystem or hard
Bringing this up again, since there were no replies before.
I've been creating more Debian 8 unprivileged containers, and they
have been working great. However, I am still encountering the annoyances
listed in my initial email. Has anyone else been running into these
issues?
Thanks,
Mathias
