From 1f25dec32626d8d8d724bfb54131b581ed0ab9c6 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 29 Mar 2016 17:15:37 -0400 Subject: update --- ...ent_6_3394c1a7a485057fda84dd910e29d90f._comment | 23 ++++++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 doc/forum/Systemd.container_produces_non-standard_systemd_container/comment_6_3394c1a7a485057fda84dd910e29d90f._comment (limited to 'doc/forum/Systemd.container_produces_non-standard_systemd_container') diff --git a/doc/forum/Systemd.container_produces_non-standard_systemd_container/comment_6_3394c1a7a485057fda84dd910e29d90f._comment b/doc/forum/Systemd.container_produces_non-standard_systemd_container/comment_6_3394c1a7a485057fda84dd910e29d90f._comment new file mode 100644 index 00000000..9ae8219c --- /dev/null +++ b/doc/forum/Systemd.container_produces_non-standard_systemd_container/comment_6_3394c1a7a485057fda84dd910e29d90f._comment @@ -0,0 +1,23 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 6""" + date="2016-03-29T21:09:25Z" + content=""" + clone NAME NAME + Clones a container or VM image. The arguments specify the + name of the image to clone and the name of the newly + cloned image. Note that plain directory container images + are cloned into subvolume images with this command. + +That seems to say that the directory that Systemd.container sets up +should be clonable too. Perhaps this is a systemd bug? + +If systemd needs a container to be loaded from a tarball in order to be +clonable this way, I guess I would not mind if Systemd.container did that +as part of its initial bootstrapping. But it is extra work so I'd like to +make sure that it's really intended to need to do that. + +(Myself, I don't care if I can't clone a container; I can delete any of them +and propellor can rebuild them, or even move the line to a different host +in config.hs to relocate the container.) +"""]] -- cgit v1.3-2-g0d8e