IBM Bluemix deployment fails for node.js app

Question

Error when deploying a simple node.js app (which works locally):

ERR     mv: cannot move ‘/tmp/node-v0.10.40-linux-x64/bin’ to ‘/tmp/staged/app/vendor/node/bin’: Directory not empty
ERR mv: cannot move ‘/tmp/node-v0.10.40-linux-x64/include’ to ‘/tmp/staged/app/vendor/node/include’: Directory not empty
ERR mv: cannot move ‘/tmp/node-v0.10.40-linux-x64/licenses’ to ‘/tmp/staged/app/vendor/node/licenses’: Directory not empty
ERR mv: cannot move ‘/tmp/node-v0.10.40-linux-x64/share’ to ‘/tmp/staged/app/vendor/node/share’: Directory not empty
OUT -----> Build failed
OUT        Your build failed!
OUT        If you're stuck, please submit a ticket so we can help:
OUT        http://ibm.biz/bluemixsupport
OUT Staging failed: Buildpack compilation step failed
ERR encountered error: App staging failed in the buildpack compile phase

This fails with both the default node buildpack and the node sdk >cf push -b sdk-for-nodejs_v2_5-20150902-1526. The cf tail logs contain only the same mv errors.

Any hints?

Can you please add to the question your package.json and manifest.ylm? — Alex da Silva, Nov 12 '15 at 23:35

score 1 · Accepted Answer · answered Nov 13 '15 at 14:46

1

What worked was to use the latest node.js buildpack:

cf push -b https://github.com/cloudfoundry/buildpack-nodejs.git

answered Nov 13 '15 at 14:46

Dmitry Sadakov

2,128
3
19
34

score 0 · Answer 2 · answered Nov 12 '15 at 22:50

0

Try using cf logs appname --recent as mentioned in the debugging staging errors for Node.js article in the link below:

https://www.ng.bluemix.net/docs/troubleshoot/debugging.html#debug_stgerr

answered Nov 12 '15 at 22:50

RandalAnders

1,431
9
16

The logs did not show anything except the `mv` errors, unfortunately. The answer was to use the latest node buildpack: – Dmitry Sadakov Nov 13 '15 at 14:46

IBM Bluemix deployment fails for node.js app

2 Answers2