diff options
| author | Joey Hess <joeyh@joeyh.name> | 2017-12-30 21:04:08 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2017-12-30 21:04:08 -0400 |
| commit | 54a85b53f65a5b11168223c9ff6157d13cf975cc (patch) | |
| tree | 07f7e138be66f20c6c25865769443a0785e6d0b8 /doc/todo/chroot_localdir_issue.mdwn | |
| parent | a83be9e1428afc7829f46ca4cf9722082ed3e378 (diff) | |
response
Diffstat (limited to 'doc/todo/chroot_localdir_issue.mdwn')
| -rw-r--r-- | doc/todo/chroot_localdir_issue.mdwn | 15 |
1 files changed, 15 insertions, 0 deletions
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]] |