From 54a85b53f65a5b11168223c9ff6157d13cf975cc Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Sat, 30 Dec 2017 21:04:08 -0400 Subject: response --- .../comment_5_70eb3b130cb1b7449083669f16452682._comment | 11 +++++++++++ doc/todo/chroot_localdir_issue.mdwn | 15 +++++++++++++++ 2 files changed, 26 insertions(+) create mode 100644 doc/forum/secret-project_deliverable/comment_5_70eb3b130cb1b7449083669f16452682._comment create mode 100644 doc/todo/chroot_localdir_issue.mdwn (limited to 'doc') diff --git a/doc/forum/secret-project_deliverable/comment_5_70eb3b130cb1b7449083669f16452682._comment b/doc/forum/secret-project_deliverable/comment_5_70eb3b130cb1b7449083669f16452682._comment new file mode 100644 index 00000000..5158dbe6 --- /dev/null +++ b/doc/forum/secret-project_deliverable/comment_5_70eb3b130cb1b7449083669f16452682._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 5""" + date="2017-12-31T00:46:49Z" + content=""" +I think this is more bad documentation on my part; +probably running propellor like that does not fully work +and only the propellor --spin method will really work currently. + +(Kind of a bug in propellor to; [[todo/chroot_localdir_issue]]) +"""]] diff --git a/doc/todo/chroot_localdir_issue.mdwn b/doc/todo/chroot_localdir_issue.mdwn new file mode 100644 index 00000000..497c7a93 --- /dev/null +++ b/doc/todo/chroot_localdir_issue.mdwn @@ -0,0 +1,15 @@ +Running "sudo ./propellor" is documented as a way to provision the local +host. However, properties involving chroots and docker hard code localdir, +so run /usr/local/propellor/propellor inside the chroot. When running +propellor this way, that may not exist, or may be from some other propellor +configuration and not know how to privision the chroot correctly. + +Should this stuff look at the path to the propellor executable that's +really being run and use it? There's also the shimdir, which is under +/usr/local/propellor and gets bind mounted into the chroot, so using +something close to the executable run by "sudo ./propellor" may be +surprising. And, exposeTrueLocaldir also uses the localdir. + +It may make more sense to detect when propellor is run this way and refuse +to provision chroots. Or to eliminate this little-used way of running +propellor entirely.. --[[Joey]] -- cgit v1.2.3