ulexus/meteor:build runs out of space on repeated build failures

[kaihendry]

Not sure why it's failing. Full log Any ideas?

/home/meteor/.node-gyp/8.13.0/include/node/v8.h:3230:22: note: declared here
                 bool SetAccessor(Local<String> name,
                      ^
/home/meteor/.node-gyp/8.13.0/include/node/v8config.h:318:3: note: in definition of macro 'V8_DEPRECATED'
   declarator __attribute__((deprecated(message)))
   ^~~~~~~~~~
  CXX(target) Release/obj.target/fibers/src/coroutine.o
  CC(target) Release/obj.target/fibers/src/libcoro/coro.o
  SOLINK_MODULE(target) Release/obj.target/fibers.node
  COPY Release/fibers.node
make: Leaving directory '/home/meteor/www/bundle/programs/server/node_modules/fibers/build'
Installed in `/home/meteor/www/bundle/programs/server/node_modules/fibers/bin/linux-x64-57/fibers.node`
> meteor-dev-bundle@0.0.0 install /home/meteor/www/bundle/programs/server
> node npm-rebuild.js
npm WARN lifecycle npm is using /usr/bin/node but there is no node binary in the current PATH. Use the `--scripts-prepend-node-path` option to include the path
 for the node binary npm was executed with.
> bcrypt@1.0.3 install /home/meteor/www/bundle/programs/server/npm/node_modules/bcrypt
> node-pre-gyp install --fallback-to-build
npm ERR! file sh
npm ERR! path sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn sh
npm ERR! bcrypt@1.0.3 install: `node-pre-gyp install --fallback-to-build`
npm ERR! spawn sh ENOENT
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!     /home/meteor/.npm/_logs/2019-02-21T09_14_32_980Z-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:

[Ulexus]

Whatever is building that is running out of disk space... this isn't terribly unlikely, since you're probably looking at multiple gigabytes of temporary space to compile that stuff.