On Tue, Mar 03, 2015 at 12:24:10AM +0100, Lennart Poettering wrote:
On Mon, 02.03.15 15:45, Erik Johnson ([email protected]) 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 [email protected] | http://saltstack.com
pgpL51MUnHJLT.pgp
Description: PGP signature
_______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
