Unable to launch binary in docker image

[phtrivier]

I'm trying to launch the flow-bin wrapper in a docker image (based on alpine)
The binary is available in node_modules (and seems to have the proper size), but spawn always throws a ENOENT.

Error: spawn /build/source/xxxx/node_modules/flow-bin/flow-linux64-v0.44.2/flow ENOENT
    at exports._errnoException (util.js:1022:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
    at onErrorNT (internal/child_process.js:359:16)
    at _combinedTickCallback (internal/process/next_tick.js:74:11)
    at process._tickCallback (internal/process/next_tick.js:98:9)
    at Module.runMain (module.js:606:11)
    at run (bootstrap_node.js:394:7)
    at startup (bootstrap_node.js:149:9)
    at bootstrap_node.js:509:3
  code: 'ENOENT',
  errno: 'ENOENT',
  syscall: 'spawn /build/source/xxx/node_modules/flow-bin/flow-linux64-v0.44.2/flow',
  path: '/build/source/xxx/node_modules/flow-bin/flow-linux64-v0.44.2/flow'

Could it be related to a missing library in my image (as in #58 ?) How could I find which file is not found ?

[amacleay]

There was a PR recently closed which was meant to demonstrate a possible fix to this issue: #68

I'm not positive, but it seems as though it wasn't actually meant to be merged - perhaps the author thought it was too much of a hack?

edit - there is still an open issue by that author in facebook/flow#3649 , but it hasn't been active in a couple of weeks.

[phtrivier]

@amacleay yes, I think that's the same issue. I ended up having to rebuild flow myself.
Closing this.