On Sat, 11 Feb 2023 21:12:33 +0100 Johannes Schauer Marin Rodrigues <josch@debian.org> wrote: > Package: debootstrap > Version: 1.0.128+nmu2 > Severity: normal > X-Debbugs-Cc: terceiro@debian.org > Control: affects -1 auto-apt-proxy mmdebstrap > > Hi, > > currently the mmdebstrap autopkgtest in experimental fails because debootstrap > cannot be run with the user namespace unshared if auto-apt-proxy is installed > and /tmp/.auto-apt-proxy-0 exists. Steps to reproduce: > > $ mmdebstrap --variant=custom --mode=unshare --setup-hook='env container=lxc debootstrap unstable "$1" http://127.0.0.1/debian' /dev/null > > The error message is: > > E: insecure cache dir /tmp/.auto-apt-proxy-0. Must be owned by UID 0 and have permissions 700 > > The reason for this error is, that debootstrap will run auto-apt-proxy which > will find that /tmp/.auto-apt-proxy-0 exists but since the user namespace of > the process is unshared, it will be owned by user "nobody" from its > perspective. > > Please provide a way to allow disabling running auto-apt-proxy when running > debootstrap. Maybe I am missing something, but debootstrap has no knowledge about auto-apt-proxy, why would debootstrap be the one responsible for disabling auto-apt-proxy? Shouldn't mmdebstrap setup a reasonable (empty) /tmp since it's the one who is setting up the unshared user namespace?
Attachment:
signature.asc
Description: PGP signature