[systemd-devel] How to deploy systemd-nspawn containers and use for deployment

Samuel Williams space.ship.traveller at gmail.com
Wed Oct 12 21:22:57 UTC 2016

I'm not sure if this belongs in machinectl, but it would be interesting to
explore some kind of deployment mechanism. e.g. machinectl deploy
local-container-name ssh://remote-server:container-name because I'm sure
this is going to be a really common use case, and there are enough details
(e.g. stopping and starting the remote machine) that it would be nice to
keep it easy for new users.

On 13 October 2016 at 02:10, Chris Bell <cwbell at narmos.org> wrote:

> On 2016-10-11 22:29, Samuel Williams wrote:
>> For step 2, what would be the best practice. Rsync the local container
>> to the remote container?
> That's worked fine for me so far. Just to state the obvious: makes sure
> the container is stopped before using rsync.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20161013/4ada2fd9/attachment-0001.html>

More information about the systemd-devel mailing list