准备包"任务是在Meteor Up的1.3.0版本中引入的(请参见

The task "Prepare bundle" was introduced in the version 1.3.0 of Meteor Up (see release notes):

将捆绑包上传到每个服务器后，将运行一个名为准备捆绑包"的新任务.它安装Meteor npm依赖项，重建本机模块，并将结果存储在docker映像中.这有一些好处:

After the bundle is uploaded to each server, a new task is run called "Prepare bundle". It installs the Meteor npm dependencies, rebuilds native modules, and stores the result in a docker image. This has a few benefits:

• 在meteor.deployCheckWaitTime中的时间不再需要包括安装npm依赖项的时间
• 当安装依赖项失败时，它不会持续重新启动，直到meteor.deployCheckWaitTime到期，并以--verbose运行会显示npm install的完整日志
• 依赖项在每次部署期间仅安装一次.这意味着mup启动，mup重新启动和mup重新配置都快得多.

• The time in meteor.deployCheckWaitTime no longer needs to include the time to install npm dependencies
• When installing dependencies fails, it does not continuously restart until meteor.deployCheckWaitTime expires, and running with --verbose shows the full logs from npm install
• Dependencies are only installed once during each deploy. This means that mup start, mup restart, and mup reconfig are all much faster.

从1.3.1版开始，可以通过在mup.js中添加选项app.docker.prepareBundle并将其设置为false来禁用此任务.几周前，我处理了相同的错误，并且通过这种解决方法，我能够将应用程序部署到DigitalOcean.

From the version 1.3.1 this task can be disabled by adding the option app.docker.prepareBundle in mup.js and setting it to false. I dealt with the same error a few weeks ago and with this workaround I was able to deploy my application to DigitalOcean.