Debian Bug report logs - #932357
debootstrap: failed to create a pbuilder base.tgz inside a systemd-nspawn unprevilledged container

Reply or subscribe to this bug.

Display info messages

Message #5 received at [email protected] (full text, mbox, reply):

From: Alberto Garcia <[email protected]>

To: Debian Bug Tracking System <[email protected]>

Subject: debootstrap: failed to create a pbuilder base.tgz inside a systemd-nspawn container

Date: Thu, 18 Jul 2019 14:20:19 +0300

Package: debootstrap
Version: 1.0.115
Severity: normal

Dear Maintainer,

here's what happens if I try to create a base.tgz inside a
systemd-nspawn container using pbuilder and debootstrap:

# pbuilder --create --mirror http://deb.debian.org/debian/ --basetgz /var/cache/pbuilder/sid-amd64.tgz --distribution sid --architecture amd64
W: /root/.pbuilderrc does not exist
I: Distribution is sid.
I: Current time: Thu Jul 18 14:12:11 EEST 2019
I: pbuilder-time-stamp: 1563448331
I: Building the build environment
I: running debootstrap
/usr/sbin/debootstrap
mknod: /var/cache/pbuilder/build/42591/test-dev-null: Operation not permitted
E: Cannot install into target '/var/cache/pbuilder/build/42591' mounted with noexec or nodev
E: debootstrap failed
E: debootstrap.log not present
W: Aborting with an error

I indeed don't have permissions to run mknod, but I see that there's
code to detect other container systems and use bind mounts and
symlinks instead.

Would that be possible in this case?

Thanks,

Berto

-- System Information:
Debian Release: 10.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.0.4-arch1-1-ARCH (SMP w/64 CPU cores; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /usr/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:
ii  arch-test               0.15-2
ii  debian-archive-keyring  2019.1
ii  gnupg                   2.2.12-1

Versions of packages debootstrap suggests:
pn  squid-deb-proxy-client  <none>
pn  ubuntu-archive-keyring  <none>

-- no debconf information

Message #10 received at [email protected] (full text, mbox, reply):

From: Hideki Yamane <[email protected]>

To: [email protected]

Subject: Re: debootstrap: failed to create a pbuilder base.tgz inside a systemd-nspawn container

Date: Sun, 23 Feb 2020 20:36:15 +0900

Hi,

 It would be succeeded inside systemd-nspawn container but fails with
 "unprivileged" container. So, could you give some information about
 difference between privileged and unprivileged container, please?
 It there's it, can detect and change its behavior.


-- 
Regards,

 Hideki Yamane     henrich @ debian.org/iijmio-mail.jp

Message #15 received at [email protected] (full text, mbox, reply):

From: Alberto Garcia <[email protected]>

To: Hideki Yamane <[email protected]>, [email protected]

Subject: Re: Bug#932357: debootstrap: failed to create a pbuilder base.tgz inside a systemd-nspawn container

Date: Mon, 9 Mar 2020 18:14:58 +0100

On Sun, Feb 23, 2020 at 08:36:15PM +0900, Hideki Yamane wrote:

>  It would be succeeded inside systemd-nspawn container but fails
>  with "unprivileged" container. So, could you give some information
>  about difference between privileged and unprivileged container,
>  please?  It there's it, can detect and change its behavior.

I'm not an expert in systemd containers, but as far as I can see when
you run an unprivileged container the root user inside a container
is actually mapped to a random (non-root) user ID and cannot create
devices, that's why mknod fails.

I don't know if fixing that check and using an alternative system is
enough to solve the problem though, a quick test shows that there are
also problems when mounting /sys inside the pbuilder chroot.

Berto

Send a report that this bug log contains spam.