<html><head></head><body> <div>The make stage could run a clean as a dependency, that way make container and make iso could be run in isolation from a clean when desired.</div><div><br></div><div>Example (in target definition)<caret></caret>:</div><div><br></div><div> make: clean <- define as a dependency in the Makefile</div><div><br></div>now make clean can be called either when desired, or as part of calling make with no arguments :)<div><br></div><div>Thus, it would be user choice. Thoughts?</div><div><br></div><div>As for the idempotency concern, this wouldn’t be an issue. The base image *only* has what you’ve specified in the dockerfile :) hope that helps.</div><div><div><br></div><div>Cheers<br><div><br></div><div><br></div><div id="protonmail_mobile_signature_block"><div>Sent from ProtonMail for iOS</div></div> <div><br></div><div><br></div>On Mon, Jul 12, 2564 at 09:03, Chris Punches <<a href="mailto:chris.punches@silogroup.org" class="">chris.punches@silogroup.org</a>> wrote:<blockquote class="protonmail_quote" type="cite"> I like the idea; so what would this look like?<br><br>make<br>make container<br>make iso<br>make clean<br><br>...?<br><br>One of the concerns at not having this be in the make stage is that<br>subsequent builds would cause different results, and could compromise<br>idempotency. If that's not accurate please let me know.<br><br>-C<br><br>On Sat, 2021-07-10 at 12:57 +0000, OmnidApps LLC wrote:<br>> Hello all,<br>><br>> Instead of docker image rm inside of build, wouldn't it be better to<br>> just make that part of the make clean stage? Reason being, the<br>> initial build does a lot of stuff which takes a bit of time. Of<br>> course, I could just comment the docker image rm line, but normally I<br>> am used to these sort of artifacts sticking around unless a clean is<br>> run.<br>><br>> Thoughts?<br>><br>> Cheers<br>><br>> Sent with ProtonMail Secure Email.<br>><br><br></blockquote><div><br></div><div><br></div></div></div></body></html>