diff options
| author | Joey Hess <joeyh@joeyh.name> | 2016-03-30 10:45:15 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2016-03-30 10:47:31 -0400 |
| commit | d08734bbbebc0211d4203922fb94384497547d3c (patch) | |
| tree | a0a32a5073d05d6ce3c67086ac7ce6948c54f3bc /doc/forum/Systemd.container_produces_non-standard_systemd_container | |
| parent | 4892d4a26c8e542c764bbc64cbe94490c96a14dc (diff) | |
| parent | adc7dad3d8b86b1ad770d1c82a66cd4df7bbee20 (diff) | |
Merge branch 'master' into typed-os-requirements
Diffstat (limited to 'doc/forum/Systemd.container_produces_non-standard_systemd_container')
3 files changed, 38 insertions, 0 deletions
diff --git a/doc/forum/Systemd.container_produces_non-standard_systemd_container/comment_5_b73901c0aa408d35346c46e523be8c3f._comment b/doc/forum/Systemd.container_produces_non-standard_systemd_container/comment_5_b73901c0aa408d35346c46e523be8c3f._comment new file mode 100644 index 00000000..61f34253 --- /dev/null +++ b/doc/forum/Systemd.container_produces_non-standard_systemd_container/comment_5_b73901c0aa408d35346c46e523be8c3f._comment @@ -0,0 +1,7 @@ +[[!comment format=mdwn + username="gueux" + subject="comment 5" + date="2016-03-28T19:39:22Z" + content=""" +The error message is one thing, but shouldn't the container built with Systemd.container be clonable? Maybe by adding an additional \"export-tar/import-tar\" step to Systemd.container or by using something different from mkchroot? +"""]] 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.) +"""]] diff --git a/doc/forum/Systemd.container_produces_non-standard_systemd_container/comment_7_5a3418e8cc800ceea5988059b6d86aff._comment b/doc/forum/Systemd.container_produces_non-standard_systemd_container/comment_7_5a3418e8cc800ceea5988059b6d86aff._comment new file mode 100644 index 00000000..e6e24c42 --- /dev/null +++ b/doc/forum/Systemd.container_produces_non-standard_systemd_container/comment_7_5a3418e8cc800ceea5988059b6d86aff._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="gueux" + subject="comment 7" + date="2016-03-30T11:32:51Z" + content=""" +After a chat session on #systemd, I've posted a new issue https://github.com/systemd/systemd/issues/2914 +There should be updates soon. +"""]] |