<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">I raised this issue back on 6th/7th
December. It was a side-issue in a discussion entitled "unable to
run systemd in an LXC container". I have always performed a
destroy/create cycle to apply changes written to
/etc/lxc/mycontainer.conf. I was asked why I didn't edit in /var
directly and I replied that I treated the files created by LXC in
/var to be internal and have always used the destroy/create cycle
for config updates. There was talk of adding a -k (keep) option to
lxc-destroy.<br>
<br>
I have been working on other commitments and need to come back and
revisit this but it's good to see others have experienced the same
difficulty when this change in behaviour.<br>
<br>
I would be interested in current thoughts.<br>
<br>
John<br>
<br>
<br>
On 07/02/13 23:27, Roland Neary wrote:<br>
</div>
<blockquote
cite="mid:zarafa.5114384d.6114.4912286700c6fbcf@marl-7.stone.gs.stone-it.local"
type="cite">
<meta name="Generator" content="Zarafa WebApp v7.0.7-34256">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<title>RE: [Lxc-users] lxc-destroy erase rootfs</title>
As it's so easy to redo a container I've come to love the
lxc-destroy command.<br>
<br>
Having said that, the huge pitfall is of course user expectation.
The first time I looked at it it did exactly what I wanted, not
what I thought it would do. <br>
<br>
<br>
<br>
<div><font face="Arial, sans-serif">Regards,</font></div>
<span style="color: rgb(0, 0, 0); font-family: Arial, sans-serif;
">
<div style="font-weight: bold; "><b style="color: rgb(0, 0, 0);
font-family: Arial, sans-serif; "><br>
</b></div>
Roland Neary</span><font face="Arial, sans-serif"><b><br>
</b></font>
<blockquote style="border-left: 2px solid #325FBA; padding-left:
5px; margin-left: 5px; margin-right: 0px;">-----Original
message-----<br>
<strong>From:</strong> Papp Tamas <a class="moz-txt-link-rfc2396E" href="mailto:tompos@martos.bme.hu"><tompos@martos.bme.hu></a><br>
<strong>Sent:</strong> Fri 08-Feb-2013 00:19<br>
<strong>To:</strong> Roland Neary <a class="moz-txt-link-rfc2396E" href="mailto:neary@stone-it.com"><neary@stone-it.com></a><br>
<strong>Cc:</strong> Christoph Willing
<a class="moz-txt-link-rfc2396E" href="mailto:cwilling@users.sourceforge.net"><cwilling@users.sourceforge.net></a>;
<a class="moz-txt-link-abbreviated" href="mailto:lxc-users@lists.sourceforge.net">lxc-users@lists.sourceforge.net</a><br>
<strong>Subject:</strong> Re: [Lxc-users] lxc-destroy erase
rootfs<br>
<br>
<pre style="white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; white-space: pre-wrap; word-wrap: break-word;" wrap="">On 02/08/2013 12:10 AM, Roland Neary wrote:
> Sorry to hear you b0rked your setup. Are you perhaps a Xen user who found out that `'xm destroy` !=
> lxc-destroy?
>
> If so, you're probably not the first....
Actually neither xen, nor virsh destroys <span style="text-decoration: underline">_data_</span> and until v0.7 (or v0.8?) lxc does it only if it was
in /var/lib/lxc.
I'm and lxc user and that's why I'm surprised.
tamas
</pre>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
<a class="moz-txt-link-freetext" href="http://p.sf.net/sfu/sophos-d2d-feb">http://p.sf.net/sfu/sophos-d2d-feb</a></pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Lxc-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Lxc-users@lists.sourceforge.net">Lxc-users@lists.sourceforge.net</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/lxc-users">https://lists.sourceforge.net/lists/listinfo/lxc-users</a>
</pre>
</blockquote>
<br>
</body>
</html>