<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Oct 27, 2017 at 11:18 AM, Gerard Ryan <span dir="ltr"><<a href="mailto:gryan@redhat.com" target="_blank">gryan@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">Matthias Wessendorf <<a href="mailto:mwessend@redhat.com">mwessend@redhat.com</a>> writes:<br>
<br>
> Hi,<br>
><br>
> I had like 15 GB of data in here:<br>
> /var/lib/origin/openshift.<wbr>local.pv/registry/docker/<wbr>registry/v2/blobs/sha256<br>
><br>
> wondering.... if that is never cleaned up, or does one run a scipt ?<br>
<br>
</span>Any idea why the space grows so large?<br></blockquote><div><br></div><div>Big data! ;-)</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
This might not be relevant, but if it's accumulating image/container<br>
layers for builds from BuildConfigs over time, there are new properties<br>
you can add to the BuildConfigSpec to limit the number of builds that<br>
will be kept, namely 'successfulBuildsHistoryLimit' and<br>
'failedBuildsHistoryLimit'.<br>
<br>
E.g. like we do here:<br>
<a href="https://github.com/feedhenry/fh-pipeline-library/blob/eb60354b4d9fb06db4134ef3cd9cb87fc5f74a7f/vars/buildWithDockerStrategy.groovy#L20..L21" rel="noreferrer" target="_blank">https://github.com/feedhenry/<wbr>fh-pipeline-library/blob/<wbr>eb60354b4d9fb06db4134ef3cd9cb8<wbr>7fc5f74a7f/vars/<wbr>buildWithDockerStrategy.<wbr>groovy#L20..L21</a></blockquote><div><br></div><div>ah, that could be handy - thanks</div><div> </div></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Project lead AeroGear.org</div></div>
</div></div>