Re: [systemd-devel] Creating containers from local .raw or tar images
On Mon, 02.03.15 23:50, Erik Johnson (e...@saltstack.com) wrote: On Mon, Mar 02, 2015 at 06:03:42PM -0500, Daurnimator wrote: AFAIK, all the pull-* commands do is download into /var/lib/machines. You could easily enough just copy things into there yourself. Or even less work: don't copy them in there at all, and pass your image directly to systemd-nspawn (which is what machinectl uses) See: http://www.freedesktop.org/software/systemd/man/systemd-nspawn.html I've done that before, but I am writing nspawn support for SaltStack (http://saltstack.com) and I need to start and stop them unattended. BTW, pretty much everything machinectl does is just invoke a couple of bus calls. If you hack support for nspawn into some software you can thus call the bus calls directly. More specifically, machinectl is primarily just a frontend for some calls from machined, others from importd and finally others from PID 1. Unfortunateky through we currently have no docs for importd's APIs (it's really new), and machined's are slightly incomplete (the newer bits are missing). Lennart -- Lennart Poettering, Red Hat ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Creating containers from local .raw or tar images
On Mon, 02.03.15 15:45, Erik Johnson (e...@saltstack.com) wrote: The machinectl pull-* commands allow you to download container images, but no such option (yet) exists for deploying from an image or tar file on your local filesystem. Are there plans to expand the machinectl pull-* commands to support either absolute file paths or file:/// URLs? My current dirty hack is to run an nginx instance that listens only on localhost, and pull from http://localhost/path/to/container.tar.gz, but this is far from ideal. You can simply place your raw or tar images in /var/lib/machines/ directly. But yeah, pretty high on my list is to add machinectl import-raw, machinectl import-tar, machinectl export-raw, machinectl export-tar, for doing this in a nice way. Lennart -- Lennart Poettering, Red Hat ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Creating containers from local .raw or tar images
AFAIK, all the pull-* commands do is download into /var/lib/machines. You could easily enough just copy things into there yourself. Or even less work: don't copy them in there at all, and pass your image directly to systemd-nspawn (which is what machinectl uses) See: http://www.freedesktop.org/software/systemd/man/systemd-nspawn.html On 2 March 2015 at 17:45, Erik Johnson e...@saltstack.com wrote: The machinectl pull-* commands allow you to download container images, but no such option (yet) exists for deploying from an image or tar file on your local filesystem. Are there plans to expand the machinectl pull-* commands to support either absolute file paths or file:/// URLs? My current dirty hack is to run an nginx instance that listens only on localhost, and pull from http://localhost/path/to/container.tar.gz, but this is far from ideal. -- Erik Johnson | Senior Engineer 3400 North Ashton Blvd, Suite 110 | Lehi, UT 84043 e...@saltstack.com | http://saltstack.com ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Creating containers from local .raw or tar images
The machinectl pull-* commands allow you to download container images, but no such option (yet) exists for deploying from an image or tar file on your local filesystem. Are there plans to expand the machinectl pull-* commands to support either absolute file paths or file:/// URLs? My current dirty hack is to run an nginx instance that listens only on localhost, and pull from http://localhost/path/to/container.tar.gz, but this is far from ideal. -- Erik Johnson | Senior Engineer 3400 North Ashton Blvd, Suite 110 | Lehi, UT 84043 e...@saltstack.com | http://saltstack.com pgpFotC_3B5wf.pgp Description: PGP signature ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Creating containers from local .raw or tar images
On Mon, Mar 02, 2015 at 06:03:42PM -0500, Daurnimator wrote: AFAIK, all the pull-* commands do is download into /var/lib/machines. You could easily enough just copy things into there yourself. Or even less work: don't copy them in there at all, and pass your image directly to systemd-nspawn (which is what machinectl uses) See: http://www.freedesktop.org/software/systemd/man/systemd-nspawn.html I've done that before, but I am writing nspawn support for SaltStack (http://saltstack.com) and I need to start and stop them unattended. -- Erik Johnson | Senior Engineer 3400 North Ashton Blvd, Suite 110 | Lehi, UT 84043 e...@saltstack.com | http://saltstack.com pgpxDnjOGH0PC.pgp Description: PGP signature ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Creating containers from local .raw or tar images
On Tue, Mar 03, 2015 at 12:24:10AM +0100, Lennart Poettering wrote: On Mon, 02.03.15 15:45, Erik Johnson (e...@saltstack.com) wrote: The machinectl pull-* commands allow you to download container images, but no such option (yet) exists for deploying from an image or tar file on your local filesystem. Are there plans to expand the machinectl pull-* commands to support either absolute file paths or file:/// URLs? My current dirty hack is to run an nginx instance that listens only on localhost, and pull from http://localhost/path/to/container.tar.gz, but this is far from ideal. You can simply place your raw or tar images in /var/lib/machines/ directly. But yeah, pretty high on my list is to add machinectl import-raw, machinectl import-tar, machinectl export-raw, machinectl export-tar, for doing this in a nice way. Lennart -- Lennart Poettering, Red Hat Nice, I figured this would be the logical next step. Right now I am writing support for managing nspawn images in SaltStack, so I was just considering possibilities for functions to add. -- Erik Johnson | Senior Engineer 3400 North Ashton Blvd, Suite 110 | Lehi, UT 84043 e...@saltstack.com | http://saltstack.com pgpL51MUnHJLT.pgp Description: PGP signature ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
