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
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
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:
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
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
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
