Report this

What is the reason for this report?

Doh! Error deploying Meteor JS 'mup deploy' command - Preparing Bundle: FAILED

Posted on December 13, 2017

Hello, when I run the following commpand: ‘mup deploy’ I get the following message after app is pushed to DO Droplet:

Started TaskList: Pushing Meteor App [46.101.82.119] - Pushing Meteor App Bundle to the Server [46.101.82.119] - Pushing Meteor App Bundle to the Server: SUCCESS [46.101.82.119] - Prepare Bundle [46.101.82.119] x Prepare Bundle: FAILED

-----------------------------------STDERR-----------------------------------
The command '/bin/sh -c cd  /built_app/programs/server &&     npm install --unsafe-perm' returned a non-zero code: 1
Error response from daemon: Cannot link to a non running container: /mongodb AS /Seen/mongodb
Error: failed to start containers: Seen
-----------------------------------STDOUT-----------------------------------
put above.
npm ERR! code ELIFECYCLE
npm ERR! errno -2
npm ERR! bcrypt@1.0.3 install: `node-pre-gyp install --fallback-to-build`
npm ERR! Exit status -2
npm ERR! 
npm ERR! Failed at the bcrypt@1.0.3 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2017-12-13T20_31_44_061Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! meteor-dev-bundle@0.0.0 install: `node npm-rebuild.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the meteor-dev-bundle@0.0.0 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2017-12-13T20_31_44_120Z-debug.log

I’m new to server-side deployment / dev so apologies if this is a fairly simple fix, I just don’t know what I’m looking for.

Kindest -Will



This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Hello,

The problem you’re experiencing seems to be related to the bcrypt package failing to install properly, which can often be a result of incompatible versions between Node.js, npm, Meteor, and bcrypt.

There are a couple of things you can try to fix the issue:

  1. Updating all packages: Sometimes, issues like these can be solved by updating all of the packages to their latest versions. This includes bcrypt, Meteor, Node.js, npm, and mup. Make sure to update them in your local development environment and also on the server.

  2. Rebuilding bcrypt: In your project directory, try removing the node_modules directory and running meteor npm install. After that, try rebuilding bcrypt with the command meteor npm rebuild bcrypt --build-from-source, then try deploying again.

  3. Using a different bcrypt version: Some users have reported problems with specific versions of bcrypt. You could try using a different version to see if that solves your problem. You can specify the version in your package.json file.

  4. Check Docker version: If you’re using Docker, make sure that it’s updated to the latest version.

  5. Increasing the Deployment Timeouts: Sometimes, the build process can take longer than expected, and mup might stop the deployment before it’s finished. You can increase the deployment timeouts in the mup.js configuration file.

Remember that these suggestions might or might not work for your specific problem, as the solution often depends on your specific setup. The key is to make sure that all the versions of the tools you’re using are compatible with each other.

The “Cannot link to a non running container” error suggests that there’s also a problem with Docker and the MongoDB container. This could be caused by an issue with Docker itself, or with the way the containers are being set up by mup. Make sure that Docker is functioning correctly and that mup is correctly configured to set up the containers. You might also want to try restarting Docker or the entire server to see if that fixes the problem.

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

Get started for free

Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

*This promotional offer applies to new accounts only.