Package: sbuild
Version: 0.78.1-1
Severity: normal

Hi,

Does sbuild works within docker?

I'm getting "Chroot setup failed" error.
Here are the steps to reproduce (within docker):

gbp clone --all --pristine-tar
g...@salsa.debian.org:go-team/packages/golang-github-ghodss-yaml.git
cd golang-github-ghodss-yaml
gbp buildpackage

More details:

-------------------------------
$ gbp buildpackage
gbp:info: Exporting 'HEAD' to
'/.../yaml/build-area/golang-github-ghodss-yaml-tmp'
gbp:info: Moving '/.../yaml/build-area/golang-github-ghodss-yaml-tmp'
to '/.../yaml/build-area/golang-github-ghodss-yaml-1.0.0'
gbp:info: Performing the build
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying fix-ftbfs-on-i386.patch
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building golang-github-ghodss-yaml using existing
./golang-github-ghodss-yaml_1.0.0.orig.tar.gz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: building golang-github-ghodss-yaml in
golang-github-ghodss-yaml_1.0.0-2.debian.tar.xz
dpkg-source: info: building golang-github-ghodss-yaml in
golang-github-ghodss-yaml_1.0.0-2.dsc
dpkg-source: info: unapplying fix-ftbfs-on-i386.patch
sbuild (Debian sbuild) 0.78.1 (09 February 2019) on 98054b26de5d

+==============================================================================+
| golang-github-ghodss-yaml 1.0.0-2 (amd64)    Sun, 17 Mar 2019 14:07:48 +0000 |
+==============================================================================+

Package: golang-github-ghodss-yaml
Version: 1.0.0-2
Source Version: 1.0.0-2
Distribution: UNRELEASED
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: full

E: 10mount: mount:
/run/schroot/mount/unstable-amd64-sbuild-ef9e6c19-47f8-4938-9b8b-aea42c31a34e:
permission denied.
E: unstable-amd64-sbuild-ef9e6c19-47f8-4938-9b8b-aea42c31a34e: Chroot
setup failed: stage=setup-start
Chroot setup failed
E: Error creating chroot session: skipping golang-github-ghodss-yaml

+------------------------------------------------------------------------------+
| Summary                                                                      |
+------------------------------------------------------------------------------+

Build Architecture: amd64
Build Type: full
Build-Space: 0
Build-Time: 0
Distribution: UNRELEASED
Fail-Stage: create-session
Host Architecture: amd64
Install-Time: 0
Job: /sysvol/dg/yaml/build-area/golang-github-ghodss-yaml_1.0.0-2.dsc
Machine Architecture: amd64
Package: golang-github-ghodss-yaml
Package-Time: 0
Source-Version: 1.0.0-2
Space: 0
Status: failed
Version: 1.0.0-2
--------------------------------------------------------------------------------
Finished at 2019-03-17T14:07:48Z
Build needed 00:00:00, 0k disk space
E: Error creating chroot session: skipping golang-github-ghodss-yaml
gbp:error: 'sbuild --source-only-changes -s -v -A --no-clean-source'
failed: it exited with 1
-------------------------------

Note again,

E: 10mount: mount:
/run/schroot/mount/unstable-amd64-sbuild-ef9e6c19-47f8-4938-9b8b-aea42c31a34e:
permission denied.
E: unstable-amd64-sbuild-ef9e6c19-47f8-4938-9b8b-aea42c31a34e: Chroot
setup failed: stage=setup-start
Chroot setup failed

I'm running all above as *root* within docker, so the "permission
denied" has to be related to using sbuild within docker.

please help.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.15.0-1012-azure (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages sbuild depends on:
ii  adduser         3.118
ii  libsbuild-perl  0.78.1-1
ii  perl            5.28.1-4

Versions of packages sbuild recommends:
pn  autopkgtest  <none>
ii  debootstrap  1.0.114
ii  schroot      1.6.10-6+b1

Versions of packages sbuild suggests:
pn  deborphan  <none>
ii  e2fsprogs  1.44.5-1
pn  kmod       <none>
ii  wget       1.20.1-1

-- no debconf information

Reply via email to