Results 1 to 2 of 2

Thread: Sencha Cmd v6.5.0.180: Failed creating background process

  1. #1
    Sencha User
    Join Date
    Oct 2016

    Default Sencha Cmd v6.5.0.180: Failed creating background process


    I get the following error when I try to build a package
    sencha -d package build
    or just run the sass command
    sencha -d ant sass
    I try to run the build inside a Docker container using Alpine 3.4.6 as base image (openjdk:8-jre-alpine):
    Linux da862b258861 4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:36 UTC 2018 x86_64 Linux
    My Sencha Cmd version is v6.5.0.180.

    Any ideas, how to solve this issue?

    [ERR] com.sencha.exceptions.ExProcess: Failed creating background process
    [ERR] at com.sencha.util.ExternalProcess.start(
    [ERR] at com.sencha.util.ProcessUtil.spawn(
    [ERR] at
    [ERR] at
    [ERR] at
    [ERR] at
    [ERR] at
    [ERR] at
    [ERR] at
    [ERR] at com.sencha.command.Sencha.dispat
    [ERR] ch(
    [ERR] Caused by: Cannot run program "/opt/Sencha/Cmd/bin/linux-x64/node/node" (in directory "/opt/Sencha/Cmd"): error=2, No such file or directory
    [ERR] at java.lang.ProcessBuilder.start(
    [ERR] at com.sencha.util.ExternalProcess.start(
    [ERR] ... 123 more
    [ERR] Caused by: error=2, No such file or directory
    [ERR] at java.lang.UNIXProcess.forkAndExec(Native Method)
    [ERR] at java.lang.UNIXProcess.<init>(
    [ERR] at java.lang.ProcessImpl.start(
    [ERR] at java.lang.ProcessBuilder.start(
    [ERR] ... 124 more
    [ERR] Total time: 3 minutes 7 seconds

  2. #2
    Sencha Premium Member
    Join Date
    Aug 2012


    I think the problem is caused by using the Alpine Docker image to run Sencha Cmd which contains executables that aren't compatible with Alpine. If you use the Stretch images, you will likely find that the error doesn't occur.

    Note about my setup, I'm using a bind mount to expose a previously installed Sencha Cmd to my container. The installer was originally run on an Ubuntu 14.04 VM. I don't know if the 'node' executable is pre-packaged or compiled and linked during installation. But I'm guessing either way the problem is due to the executable being linked against glibc whereas Alpine goes to great lengths to avoid glibc.

    I haven't tried, but you may have luck running the installer as part of building the image instead of bind mounting it from the host. I doubt that would work, though. Seems like there are a lot of assumptions being made in the Sencha Cmd installer that wouldn't hold up.

    I think the ideal solution would be for Sencha to provide Docker images including Alpine flavors, but I'm not sure the amount of work that would entail either.

Similar Threads

  1. Replies: 1
    Last Post: 6 Feb 2017, 3:23 PM
  2. Replies: 4
    Last Post: 13 Mar 2015, 9:46 AM
  3. Replies: 0
    Last Post: 13 Mar 2015, 7:20 AM
  4. Sencha Cmd v5.0.2.270 - Failed creating background process
    By catalinux1907 in forum Sencha Cmd
    Replies: 1
    Last Post: 10 Oct 2014, 12:21 PM
  5. Replies: 4
    Last Post: 7 Mar 2014, 1:57 PM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts