On 2017-04-07 06:41, Serge E. Hallyn wrote:
would you mind opening an issue for this at github.com/lxc/lxd/issues?
Just add in all the info you have and, if I understand right that you
can't put time into further reproductions, just say so up top so
hopefully we won't bug you too much.
Here
Quoting Tomasz Chmielewski (man...@wpkg.org):
> On 2017-03-13 06:28, Benoit GEORGELIN - Association Web4all wrote:
> >Hi lxc-users ,
> >
> >I would like to know if you have any experience with a large number of
> >LXC/LXD containers ?
> >In term of performance, stability and limitation .
> >
>
I have a particular distribution based on CentOS 7 that I would like to
turn into a LXD container. The post from Stephane Graber here below has
a section titled Manually building an image, but it gives some pretty
generic steps that I'm not entirely familiar with. I'm hoping someone
could
On 04/05/2017 06:45 AM, Serge E. Hallyn wrote:
I correct in assuming LXC *does* provide a means to enable RT
The kernel has hardcoded checks (which are not namespaced) that
if you are not (global) root, you cannot set or change the rt
policy. I suspect there is a way that could be safely
Dear Nicholas,
there's no real difference in proposed procedure, just use lxc-execude to enter
a containers enviroment (, i.e. set of namespaces). Or use lxc-attach to attach
to a console login of the running container
with greetings
Guido
On 06.04.2017 16:01, Nicholas Chambers wrote:
> My
My bad! I didn't realize there was a difference. At the moment I am
working with lxc. Also, I forgot to mention, I would ideally like to
make an unprivledged container, but can make a privledged container if
necessary.
On 4/5/17 7:20 PM, Spike wrote:
are you suing lxc or lxd? in case it
I can confirm that we for sure also depend on the stable 2.0 in xenial.
It actually is very easy to install a more recent version nested in 2.0 for
specific use cases.
2017-04-05 23:53 GMT+02:00 Stéphane Graber :
> Yes, it would be.
>
> I also disagree that it's what most