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

What about rkt with systemd? https://coreos.com/rkt/docs/latest/using-rkt-with-systemd.html Any experiences? On Thu, Oct 20, 2016 at 2:02 PM, Lennart Poettering wrote: > On Thu, 20.10.16 12:35, Juanjo Presa (juan...@gmail.com) wrote: > > > I am comfortable with

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

On Thu, 20.10.16 12:35, Juanjo Presa (juan...@gmail.com) wrote: > I am comfortable with machinectl nowadays but maybe I miss some kind of > versioning of images generated. Do you have any advice or recommendation > about this? Versioning is hard. We have no concept for that in nspawn/machined,

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

I am comfortable with machinectl nowadays but maybe I miss some kind of versioning of images generated. Do you have any advice or recommendation about this? On Thu, Oct 20, 2016 at 2:41 AM, Nathan Williams wrote: > Fwiw, if you're using Chef, the impending release of v3

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

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 wrote: > On Thu, 13.10.16 01:09, Brian Kroth

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

On Thu, 13.10.16 10:22, Samuel Williams (space.ship.travel...@gmail.com) wrote: > 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

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

On Wed, 12.10.16 15:29, Samuel Williams (space.ship.travel...@gmail.com) wrote: > Hello. > > I've been thinking about how I could use systemd-nspawn containers. > > Ideally, we have a local container which can then be pushed to one or more > VPS instances. > > An example workflow might look

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

On Thu, 13.10.16 01:09, Brian Kroth (bpkr...@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 a >

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

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 a send/recv of a golden snapshot. Possibly also for an lvm volume/snapshot. For

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

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.

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

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.

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

Hello. I've been thinking about how I could use systemd-nspawn containers. Ideally, we have a local container which can then be pushed to one or more VPS instances. An example workflow might look like this: - Step 1: On development box, update some software in a container and test. It's okay.