[systemd-devel] directory for machine templates

Johannes Ernst johannes.ernst at gmail.com
Tue Aug 18 14:30:04 PDT 2015


/var/lib/machines is intended to be, as I understand it, for (virtual) machines that are or could be started at every boot.

Would it make sense to have a similar convention for templates?

Use cases:
1. Testing. Pull base image once, run lots of containers from the same base image
2. Hosting. Pull common base image(s) once, let customers instantiate lots of containers from the same base image(s)

It could work like this, with -T (template) in analogy to -M (machine):

$ system-nspawn -T fedora-xyz -M fedora-test123

where /var/lib/machine-templates/fedora-xyz is the file downloaded with something like:

$ machinectl pull-raw-template http://../fedora-xyz <http://../fedora-xyz>

Just a thought.

Cheers,



Johannes.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20150818/6285a26c/attachment.html>


More information about the systemd-devel mailing list