Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Builde error: no such file or directory #1141

Closed
mauro-ni opened this issue Sep 18, 2017 · 2 comments
Closed

Builde error: no such file or directory #1141

mauro-ni opened this issue Sep 18, 2017 · 2 comments
Labels

Comments

@mauro-ni
Copy link

Info:

  • Docker version ($ docker --version): Docker version 17.06.2-ce, build cec0b72
  • Laradock commit ($ git rev-parse HEAD): ae048e6
  • System info (Mac, PC, Linux): Mac
  • System info disto/version: macOS Sierra 10.12.6

Issue:

Build error after laradock upgrade.


Expected behavior:

Successful build.


Reproduce:

docker-compose build --no-cache nginx mysql phpmyadmin workspace php-fpm applications


Relevant Code:

npm ERR! path /home/laradock/.nvm/versions/node/v8.5.0/lib/node_modules/vue-cli/node_modules/js-beautify/js/bin/css-beautify.js
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall chmod
npm ERR! enoent ENOENT: no such file or directory, chmod '/home/laradock/.nvm/versions/node/v8.5.0/lib/node_modules/vue-cli/node_modules/js-beautify/js/bin/css-beautify.js'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/laradock/.npm/_logs/2017-09-18T12_34_22_427Z-debug.log
ERROR: Service 'workspace' failed to build: The command '/bin/sh -c if [ ${INSTALL_NODE} = true ]; then     curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.1/install.sh | bash &&         . $NVM_DIR/nvm.sh &&         nvm install ${NODE_VERSION} &&         nvm use ${NODE_VERSION} &&         nvm alias ${NODE_VERSION} &&         npm install -g gulp bower vue-cli ;fi' returned a non-zero code: 254
@stale
Copy link

stale bot commented Feb 2, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the Stale label Feb 2, 2020
@stale
Copy link

stale bot commented Feb 23, 2020

Hi again 👋 we would like to inform you that this issue has been automatically closed 🔒 because it had not recent activity during the stale period. We really really appreciate your contributions, and looking forward for more in the future 🎈.

@stale stale bot closed this as completed Feb 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant