• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
UBports Robot Logo UBports Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

Trying to setup clickable with chroot

Scheduled Pinned Locked Moved App Development
3 Posts 2 Posters 1.5k Views 1 Watching
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • T Offline
      tomoqv
      last edited by 2 Jun 2017, 13:56

      I have installed a bunch of things, including click chroot create...
      When I try to build my webapp I get:
      ..$ clickable build

      Failed to create the build directory: <type 'exceptions.OSError'>
      E: 10mount: mount: unknown filesystem type 'overlayfs'
      E: 15binfmt: update-binfmts: unable to open /var/run/schroot/mount/click-ubuntu-sdk-15.04-armhf-47ad9435-1a0c-4364-993f-1db049f4a02e/bin/sh: No such file or directory
      E: click-ubuntu-sdk-15.04-armhf-47ad9435-1a0c-4364-993f-1db049f4a02e: Chroot setup failed: stage=setup-start
      Command returned 1: schroot -c click-ubuntu-sdk-15.04-armhf -- env DEB_BUILD_GNU_TYPE=x86_64-linux-gnu DEB_HOST_GNU_SYSTEM=linux-gnueabihf DEB_TARGET_ARCH_ENDIAN=little DEB_BUILD_ARCH=amd64 DEB_HOST_ARCH_CPU=arm DEB_TARGET_GNU_SYSTEM=linux-gnueabihf DEB_BUILD_ARCH_OS=linux DEB_BUILD_ARCH_CPU=amd64 DEB_TARGET_ARCH_OS=linux DEB_TARGET_ARCH_BITS=32 DEB_HOST_GNU_CPU=arm DEB_BUILD_GNU_SYSTEM=linux-gnu DEB_BUILD_ARCH_BITS=64 DEB_TARGET_MULTIARCH=arm-linux-gnueabihf DEB_BUILD_MULTIARCH=x86_64-linux-gnu DEB_HOST_GNU_TYPE=arm-linux-gnueabihf DEB_HOST_ARCH=armhf DEB_HOST_ARCH_ENDIAN=little DEB_TARGET_GNU_CPU=arm DEB_HOST_ARCH_OS=linux DEB_HOST_MULTIARCH=arm-linux-gnueabihf DEB_TARGET_GNU_TYPE=arm-linux-gnueabihf DEB_HOST_ARCH_BITS=32 DEB_TARGET_ARCH=armhf DEB_BUILD_ARCH_ENDIAN=little DEB_BUILD_GNU_CPU=x86_64 DEB_TARGET_ARCH_CPU=arm cmake /home/tomas/Dropbox/Ubuntu-Touch/App-dev/homeassistant-local
      Traceback (most recent call last):
      File "/home/tomas/Dropbox/Ubuntu-Touch/clickable-master/clickable", line 639, in <module>
      getattr(clickable, COMMAND_HANDLERS[command])()
      File "/home/tomas/Dropbox/Ubuntu-Touch/clickable-master/clickable", line 404, in build
      self._build()
      File "/home/tomas/Dropbox/Ubuntu-Touch/clickable-master/clickable", line 454, in _build
      self.run_container_command('cmake {}'.format(self.cwd))
      File "/home/tomas/Dropbox/Ubuntu-Touch/clickable-master/clickable", line 234, in run_container_command
      subprocess.check_call(shlex.split(wrapped_command), **kwargs)
      File "/usr/lib/python2.7/subprocess.py", line 541, in check_call
      raise CalledProcessError(retcode, cmd)
      subprocess.CalledProcessError: Command '['click', 'chroot', '-a', 'armhf', '-f', 'ubuntu-sdk-15.04', 'run', 'cmake', '/home/tomas/Dropbox/Ubuntu-Touch/App-dev/homeassistant-local']' returned non-zero exit status 1

      What is wrong?

      M 1 Reply Last reply 2 Jun 2017, 14:35 Reply Quote 0
      • M Offline
        mikhael @tomoqv
        last edited by mikhael 6 Feb 2017, 14:36 2 Jun 2017, 14:35

        @tomoqv said in Trying to setup clickable with chroot:

        E: 10mount: mount: unknown filesystem type 'overlayfs'

        I've had the same issue when building Cordova apps. I think the problem is with schroot package that is used by SDK. I solved it by installing original 16.04 (not 16.04.2) image into virtual machine and then Not updating it.

        T 1 Reply Last reply 4 Jun 2017, 20:51 Reply Quote 0
        • T Offline
          tomoqv @mikhael
          last edited by 4 Jun 2017, 20:51

          @mikhael said in Trying to setup clickable with chroot:

          @tomoqv said in Trying to setup clickable with chroot:

          E: 10mount: mount: unknown filesystem type 'overlayfs'

          I've had the same issue when building Cordova apps. I think the problem is with schroot package that is used by SDK. I solved it by installing original 16.04 (not 16.04.2) image into virtual machine and then Not updating it.

          I think fiddling with virtual machines sounds like a lot of hassle and something that just eats up resources from the system. There should be an easier way, and I thought installing chroot was it.

          When chroot failed, I tried to set up an lxd container as suggested in the wiki, but I ran into errors with that too. I have an Ubuntu 16.10 system and just looking for the easiest way to set up a dev environment with clickable. Unfortunately setting up an environment for ubuntu app development seems to require more than my intermediate Ubuntu skills.

          Now I have chroot and lxd + containers installed that won't start. Is there a way to just clean everything out and start over?

          1 Reply Last reply Reply Quote 0
          3 out of 3
          • First post
            3/3
            Last post