File System Error when deploying git

Shayner2005 · June 27, 2020, 3:54am

Running into a file system error when following this guide

running git push balena master rather than resin master.

Blockquote
[file-manager] npm ERR!
[file-manager] errno -2
[file-manager]
[file-manager] npm
[file-manager] ERR!
[file-manager] enoent
[file-manager] ENOENT: no such file or directory, chmod ‘/usr/local/lib/node_modules/node-file-manager/node-file-manager/bin/node-file-manager.sh’
[file-manager] npm ERR!
[file-manager] enoent
[file-manager] This is related to npm not being able to find a file.
[file-manager] npm ERR! enoent
[file-manager]
[file-manager]
[file-manager]
[file-manager] npm
[file-manager] ERR! A complete log of this run can be found in:
[file-manager]
[file-manager] npm
[file-manager] ERR! /root/.npm/_logs/2020-06-27T03_49_47_539Z-debug.log
[file-manager]
[file-manager] The command ‘/bin/sh -c npm install --unsafe-perm -g node-file-manager’ returned a non-zero code: 254
[Info] Uploading images
[Success] Successfully uploaded images
[Error] Some services failed to build:
[Error] Service: file-manager
[Error] Error: The command ‘/bin/sh -c npm install --unsafe-perm -g node-file-manager’ returned a non-zero code: 254
[Info] Built on arm01
[Error] Not deploying release.

remote: error: hook declined to update refs/heads/master
To git.balena-cloud.com:g_shayne_smith/boombeastic.git
! [remote rejected] master -> master (hook declined)
error: failed to push some refs to ‘git.balena-cloud.com:g_shayne_smith/boombeastic.git’

not sure how to access the logs.
Thanks

roman-mazur · June 29, 2020, 9:43am

Hey, boombeastic uses this npm package for the file manager functionality:

And it looks like it has a weird reference to the sh file mentioned in the error message (that reference tries to escape the project root):

github.com

efeiefei/node-file-manager/blob/master/package.json#L10


{
  "name": "node-file-manager",
  "version": "0.4.6",
  "description": "File manager web based on Koa and Angular.js",
  "main": "index.js",
  "scripts": {
    "start": "node --harmony ./lib/index.js"
  },
  "bin": {
    "node-file-manager": "../node-file-manager/bin/node-file-manager.sh"
  },
  "dependencies": {
    "co": "^4.6.0",
    "co-busboy": "1.3.1",
    "co-from-stream": "0.0.0",
    "co-fs": "^1.2.0",
    "co-fs-extra": "^1.1.0",
    "co-views": "^2.1.0",
    "ejs": "^2.3.4",
    "jszip": "^3.1.3",

I think it should be simply bin/node-file-manager.sh instead.

Maybe this was working with older npm versions before, but definitely does not work now.
The correct way would be to fix it in the node-file-manager module, but I cannot submit a pull request because github is having issues

Another way to fix this might be trying a base image with an older NPM version.

Shayner2005 · June 29, 2020, 8:57pm

How do I go about this?

iamsolankiamit · June 30, 2020, 8:03am

Hey, as Roman suggested I have created a PR with the fix. Once it is merged, a re-build will fix it.

Shayner2005 · July 5, 2020, 9:57pm

Can the repository be forked until the original is merged? What file would I change to redirect to the fork itself?

rahul-thakoor · July 6, 2020, 9:00am

Hey there,
I would recommend waiting for the upstream PR to be merged and using that.

But to answer your question, here is the workaround:
Change the line RUN npm install --unsafe-perm -g node-file-manager here to RUN npm install -g https://github.com/iamsolankiamit/node-file-manager/tarball/patch-1

The boombastic project should now build successfully.

Thanks!