<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 21, 2016 at 12:55 PM, R P Herrold <span dir="ltr"><<a href="mailto:herrold@owlriver.com" target="_blank">herrold@owlriver.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">running a child container within a parent container<br>
under Libvirt is relatiely recent (last year or two). </blockquote><div><br></div><div>So, I'm not hip to all the lingo, but I think I've figured out that "containers" (including Docker?) use the same base kernel as the host (vs., say, UML -- where the kernel that the nested environment runs in/on is independent of the hosting kernel). I need to run the environment on the legacy kernel that was part of (or, rather, directly based on that of) the legacy distribution -- not only to ensure that the development/testing environment is as similar as possible to the target deployment environment (an embedded system), but also because I've found that legacy distribution doesn't play well with the newer kernels (especially the 64-bit ones).</div><div><br></div><div><br></div></div></div></div>