Dave Miner wrote: > I don't believe there's a way to not populate the download cache, but it > will be cleaned up after the package installation if the image has the > flush-content-cache-on-success property set to True. So we do need to > include some overhead in the calculation to account for it, and perhaps > 20% isn't too far off ;-)
The files have to be stored somewhere before installation starts, the download cache just happens to be that place. If, as Dave pointed out, you have flush-content-cache-on-success set to True, you've essentially turned the download cache into a fancy /tmp directory. -- Shawn Walker
