[Bug 1319790] Re: Support HOME != /home in click chroot

[Francis Ginther]

I'm seeing a similar problem which is causing issues setting up build
automation on the ci jenkins server (http://s-jenkins.ubuntu-ci:8080).
In my case, I was able to create the chroot from my home directory
without issue, but jenkins runs it's builds from a different mount not
covered by the default fstab file (in this case /iSCSI/storage). The
failure looks like:

+ bzr branch lp:pay-ui trunk
Branched 3 revisions.
+ cd trunk
+ mkdir build
+ cd build/
+ sudo click chroot -ai386 -fubuntu-sdk-14.10 run cmake -DCLICK_MODE=on -DINSTALL_TESTS=off ..
E: Failed to change to directory ���/iSCSI/storage/jenkins/workspace/pay-ui-click-chroot/trunk/build���: No such file or directory
I: The directory does not exist inside the chroot.  Use the --directory option to run the command in a different directory.
Command returned 1: schroot -c click-ubuntu-sdk-14.10-i386 -- env DEB_HOST_MULTIARCH=i386-linux-gnu DEB_HOST_GNU_TYPE=i686-linux-gnu DEB_HOST_GNU_CPU=i686 DEB_BUILD_ARCH_OS=linux DEB_BUILD_ARCH_CPU=i386 DEB_HOST_ARCH=i386 DEB_BUILD_ARCH=i386 DEB_BUILD_GNU_TYPE=i686-linux-gnu DEB_HOST_ARCH_OS=linux DEB_HOST_GNU_SYSTEM=linux-gnu DEB_BUILD_MULTIARCH=i386-linux-gnu DEB_BUILD_ARCH_BITS=32 DEB_BUILD_ARCH_ENDIAN=little DEB_HOST_ARCH_ENDIAN=little DEB_HOST_ARCH_BITS=32 DEB_BUILD_GNU_CPU=i686 DEB_BUILD_GNU_SYSTEM=linux-gnu DEB_HOST_ARCH_CPU=i386 cmake -DCLICK_MODE=on -DINSTALL_TESTS=off ..


/iSCSI/storage/jenkins/workspace/pay-ui-click-chroot/trunk/build is the CWD when the click chroot run command is executed.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to click in Ubuntu.
https://bugs.launchpad.net/bugs/1319790

Title:
  Support HOME != /home in click chroot

Status in “click” package in Ubuntu:
  New

Bug description:
  The custom /etc/schroot/click/fstab used by click to drive schroot
  leads to problems if the user is using a different HOME than /home.
  This will lead e.g. "click chroot -aarmhf create " to fail when it
  tries to run "/finish.sh" after the initial debootstrap because the
  CWD is not available inside the schroot.

  This might be the reason for some of the bugreport around click chroot
  (like
  https://bugs.launchpad.net/ubuntu/+source/click/+bug/1299732/comments/4).

  I'm not quite sure what the best course of action is here, my current approach would be to generate the file on each
  click chroot invocation instead of shipping a static file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click/+bug/1319790/+subscriptions