[systemd-devel] How to deploy systemd-nspawn containers and use for deployment
juanjop at gmail.com
Thu Oct 20 10:35:48 UTC 2016
I am comfortable with machinectl nowadays but maybe I miss some kind of
versioning of images generated. Do you have any advice or recommendation
On Thu, Oct 20, 2016 at 2:41 AM, Nathan Williams <nath.e.will at gmail.com>
> Fwiw, if you're using Chef, the impending release of v3 of the systemd
> cookbook has a machine_image and a machine resource, which use importd and
> nspawn under the hood.
> On Wed, Oct 19, 2016, 3:45 PM Lennart Poettering <lennart at poettering.net>
>> On Thu, 13.10.16 01:09, Brian Kroth (bpkroth at gmail.com) wrote:
>> > Seems really dependent upon the container layout as to what's the most
>> > appropriate way of doing that. For instance, if the underlying fs of the
>> > source container is something like btrfs or zfs you could imagine doing
>> > send/recv of a golden snapshot. Possibly also for an lvm
>> > For others rsync might be best. For others maybe it's just a deployment
>> > script or tar or git repo.
>> Yeah, to make this clear: I doubt we should really be in the
>> deployment business too much. That's for other people to solve, for
>> example rkt.
>> However, I do think the most basic bits should probably be available,
>> simply to get developers off the ground for the most basic testing. I
>> figure that means "machinectl migrate" (as suggested in the other
>> mail) is really as good as it might get, and anything fancier should
>> really be left to other projects.
>> Lennart Poettering, Red Hat
>> systemd-devel mailing list
>> systemd-devel at lists.freedesktop.org
> systemd-devel mailing list
> systemd-devel at lists.freedesktop.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the systemd-devel