-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
libpam-tmpdir breaks grml-debootstrap #232
Comments
Yes. Using grml-debootstrap with Good enough for me but maybe you also want a general bugfix for everyone. |
Unfortunately, this is insufficient. Later on, dracut installation is failing.
|
Added to function
That helped a bit but still having dracut issues.
|
Even a workaround prepending:
does not help. |
That is actually a different issue: |
I managed to fix grml-debootstrap comparability with
Now works for me. Image is bootable. |
TODO, in short: implement as previously discussed in #234
|
avoid host environment variables such as TMP to leak into the chroot fixes grml#232
avoid host environment variables such as TMP to leak into the chroot fixes grml#232
…nto the chroot Some implementation notes: If we use `env -i`, then we can no longer export shell functions. So export -f "error_handler" had to be removed. `PATH` needs to be set, otherwise `clean_chroot "$MNTPOINT" grub-install` would fail, because grub-install is in /usr/sbin/grub-install in the chroot. http_proxy has to be passed otherwise apt-cacher-ng would be broken by this commit. While at it, I completed it and added https_proxy, and ALL_PROXY there too for completeness sake. Which environment variables are passed into the chroot is currently hardcoded. FTR, I was also wondering if it was better to use a similar mechanism to the one you're using for CHROOT_VARIABLES, but that would not work because only the chroot-script reads those. But we're not only using that but also other calls from grml-debootstrap to chroot (now clean_chroot), so the environment variables need to be set at the grml-debootstrap level. Closes: #232
https://packages.debian.org/bookworm/libpam-tmpdir installed on the host operating system breaks grml-debootstrap.
Running:
before:
Fixes this.
For the purpose of a PR to fix this:
Can I add this mkdir unconditionally or should this only be done conditionally if using libpam-tmpdir (in that case environment variables TMP, TEMP and TMPDIR will be set accordingly already).
I will also investigate alternative solutions. 1 comes to mind. Maybe installing libpam-tmpdir inside the chroot would prevent this too. Will test.
The text was updated successfully, but these errors were encountered: