[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#840372: debootstrap: second-stage fails within systemd-nspawn: proc already mounted



Package: debootstrap
Version: 1.0.81~bpo8+1
Severity: normal

Dear Maintainer,

I'm currently trying to first debootstrap with --foreign
("$ sudo debootstrap --foreign sid ./"). And then I'm trying to perform the second stage
with qemu-user-static + systemd-nspawn, which fails, unfortunately:

~~~~
$ sudo systemd-nspawn --bind /usr/bin/qemu-x86_64-static -D ./ /debootstrap/debootstrap --second-stage
Spawning container amd64 on /srv/nfs/debian-sid-test/.amd64.
Press ^] three times within 1s to kill container.
/etc/localtime is not a symlink, not updating container timezone.
I: Keyring file not available at /usr/share/keyrings/debian-archive-keyring.gpg; switching to https mirror https://mirrors.kernel.org/debian
W: Failure trying to run:  mount -t proc proc /proc
W: See //debootstrap/debootstrap.log for details
~~~~~

The following workaround helps though:

~~~~
$ sudo systemd-nspawn --bind /usr/bin/qemu-x86_64-static -D "./.amd64/" /bin/bash -c "mkdir /tmp/proc; mount --move /proc /tmp/proc; /debootstrap/debootstrap --second-stage"
~~~~

So it looks like systemd-nspawn already took care of mounting /proc and
debootstrap fails when trying to do the same? Maybe debootstrap could
just skip mounting /proc if this mount is already present?

Regards, Linus


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

Kernel: Linux 4.7.0-0.bpo.1-amd64 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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.16-1+deb8u1

Versions of packages debootstrap recommends:
ii  debian-archive-keyring  2014.3
ii  gnupg                   1.4.18-7+deb8u3

debootstrap suggests no packages.

-- no debconf information


Reply to: