<div class="gmail_quote">On 27 March 2012 15:08, Serge Hallyn <span dir="ltr"><<a href="mailto:serge.hallyn@canonical.com">serge.hallyn@canonical.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">Another option would be to copy an upstart or sysvinit script into</div>
/var/lib/lxc/$host/root/etc/init{,.d}/ which does your bootstrapping<br>
and removes itself when done.  Then just lxc-start the container.<br>
</blockquote></div><div><br></div><div><br><br><div class="gmail_quote">On 27 March 2012 15:24, Jäkel, Guido <span dir="ltr"><<a href="mailto:G.Jaekel@dnb.de">G.Jaekel@dnb.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
if it's the common way you want to setup&bootstrap a new container, maybe you can -- as a third way -- inject a (self-deleting?) script  into the containers filesystem before the first start.</blockquote></div></div>
<div><br></div>This sounds sensible, similar to CloudInit[1].  Might be a consideration in installing/forking as part of the lxc templates?<br><br>Peter<br clear="all"><div>[1] <a href="https://help.ubuntu.com/community/CloudInit">https://help.ubuntu.com/community/CloudInit</a></div>
<div><br></div>-- <br><div><span>Peter Gillard-Moss</span></div><div><span>Developer | ThoughtWorks Studios | Technical Solutions</span><br><a href="http://www.thoughtworks-studios.com/" target="_blank"><span style="color:blue">http://www.thoughtworks-studios.com</span></a></div>
<br>