[systemd-devel] Creating containers from local .raw or tar images
quae at daurnimator.com
Mon Mar 2 15:03:42 PST 2015
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)
On 2 March 2015 at 17:45, Erik Johnson <erik at 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
> erik at saltstack.com | http://saltstack.com
> systemd-devel mailing list
> systemd-devel at lists.freedesktop.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the systemd-devel