<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Definitely. And the underlying superstructure <i class="">is</i> Cgroups. </div><div class=""><br class=""></div><div class="">(I should’ve paid more attention in RHEL “Performance Tuning” class.)</div><div class=""><br class=""></div><div class="">:)</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">—j</div><div class=""><br class=""></div><br class=""><div><blockquote type="cite" class=""><div class="">On Jan 8, 2018, at 12:16 PM, Ed Cashin via Ale <<a href="mailto:ale@ale.org" class="">ale@ale.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Hmm. Containers are really just a mechanism to make advancements in process isolation easier to use.<div class="">...</div><div class="">Usually I think of it as a choice between running a process in the global namespace or running the process with more isolation via cgroups, filesystem namespaces, etc. Running containers is really just running processes, like running a process in chroot but less broken.</div><div class=""> </div></div></div></blockquote></div></body></html>