<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">/var/lib/machines is intended to be, as I understand it, for (virtual) machines that are or could be started at every boot.<div class=""><br class=""></div><div class="">Would it make sense to have a similar convention for templates?</div><div class=""><br class=""></div><div class="">Use cases:</div><div class="">1. Testing. Pull base image once, run lots of containers from the same base image</div><div class="">2. Hosting. Pull common base image(s) once, let customers instantiate lots of containers from the same base image(s)</div><div class=""><br class=""></div><div class="">It could work like this, with -T (template) in analogy to -M (machine):</div><div class=""><br class=""></div><div class="">$ system-nspawn -T fedora-xyz -M fedora-test123</div><div class=""><br class=""></div><div class="">where /var/lib/machine-templates/fedora-xyz is the file downloaded with something like:</div><div class=""><br class=""></div><div class="">$ machinectl pull-raw-template <a href="http://../fedora-xyz" class="">http://../fedora-xyz</a></div><div class=""><br class=""></div><div class="">Just a thought.</div><div class=""><br class=""></div><div class="">Cheers,</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Johannes.</div><div class=""><br class=""></div></body></html>