Package: debootstrap Version: 1.0.114 Severity: normal It seems that with the latest change to the systemd journaling configuration, that chroots no longer build with a user-owned target directory. For example: git clone https://salsa.debian.org/installer-team/debootstrap.git debootstrap.git export DEBOOTSTRAP_DIR=`pwd`/debootstrap.git mkdir unstable-chroot sudo -E ./debootstrap.git/debootstrap unstable ./unstable-chroot/ http://mirrors.linode.com/debian Ends with: W: Failure trying to run: chroot "/home/roberto/unstable-chroot" dpkg --force-overwrite --forc e-confold --skip-same-version --install /var/cache/apt/archives/libapparmor1_2.13.3-7_amd64.de b /var/cache/apt/archives/libargon2-1_0~20171227-0.2_amd64.deb /var/cache/apt/archives/libcryp tsetup12_2%3a2.2.2-3_amd64.deb /var/cache/apt/archives/libip4tc2_1.8.4-2_amd64.deb /var/cache/ apt/archives/libjson-c4_0.13.1+dfsg-6_amd64.deb /var/cache/apt/archives/libkmod2_26+20191223-1 _amd64.deb /var/cache/apt/archives/libcap2_1%3a2.27-1_amd64.deb /var/cache/apt/archives/dmsetu p_2%3a1.02.167-1_amd64.deb /var/cache/apt/archives/libdevmapper1.02.1_2%3a1.02.167-1_amd64.deb /var/cache/apt/archives/libssl1.1_1.1.1d-2_amd64.deb /var/cache/apt/archives/systemd_244.1-3_ amd64.deb W: See /home/roberto/unstable-chroot/debootstrap/debootstrap.log for details (possibly the pac kage systemd is at fault) The end of debootstrap.log, then contains: Detected unsafe path transition / -> /var during canonicalization of /var/log/journal. Detected unsafe path transition / -> /var during canonicalization of /var/log/journal. Detected unsafe path transition / -> /var during canonicalization of /var/log/journal. Detected unsafe path transition / -> /var during canonicalization of /var/log/journal. dpkg: error processing package systemd (--install): installed systemd package post-installation script subprocess returned error exit status 73 Processing triggers for libc-bin (2.29-9) ... Errors were encountered while processing: systemd However, prefixing the 'mkdir' command with 'sudo' or simply choosing to let debootstrap create the directory results in a successful chroot creation. Perhaps debootstrap should give a meaningful/helpful error message if the user attempts to create a chroot into a target directory that is not owned by root (or that has whatever attributes seem to be upsetting systemd here). Regards, -Roberto -- System Information: Debian Release: 10.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages debootstrap depends on: ii wget 1.20.1-1.1 Versions of packages debootstrap recommends: pn arch-test <none> ii debian-archive-keyring 2019.1 ii gnupg 2.2.12-1+deb10u1 Versions of packages debootstrap suggests: pn squid-deb-proxy-client <none> pn ubuntu-archive-keyring <none> -- no debconf information
Attachment:
signature.asc
Description: PGP signature