ENOSPC: no space available

I’m attempting to use Gitlab CIs build tool to automatically expo publish when merging to master. I’ve followed the documentation, and it simply doesn’t work. I’ve slowly worked through it, and have it nearly working, but it fails during expo publish.

The fail message:

$ npx expo publish --non-interactive
[15:58:02] Unable to find an existing Expo CLI instance for this directory, starting a new one...
[15:58:07] Starting Metro Bundler on port 19001.
[15:58:07] Publishing to channel 'default'...
[15:58:08] Building iOS bundle
[15:58:23] internal/fs/watchers.js:170
[15:58:23]     throw error;
[15:58:23]     ^
[15:58:23] Error: ENOSPC: no space left on device, watch '/builds/natez/dssi-mobile-lab/node_modules/@babel/register/node_modules/core-js/es/array-buffer'
[15:58:23]     at FSWatcher.start (internal/fs/watchers.js:164:26)
[15:58:23]     at Object.watch (fs.js:1232:11)
[15:58:23]     at NodeWatcher.watchdir (/builds/natez/dssi-mobile-lab/node_modules/sane/src/node_watcher.js:175:20)
[15:58:23]     at Walker.<anonymous> (/builds/natez/dssi-mobile-lab/node_modules/sane/src/common.js:116:12)
[15:58:23]     at Walker.emit (events.js:182:13)
[15:58:23]     at /builds/natez/dssi-mobile-lab/node_modules/walker/lib/walker.js:69:16
[15:58:23]     at go$readdir$cb (/builds/natez/dssi-mobile-lab/node_modules/graceful-fs/graceful-fs.js:162:14)
[15:58:23]     at FSReqWrap.oncomplete (fs.js:141:20)
[15:58:24] socket hang up
[15:58:24] Error: socket hang up
    at createHangUpError (_http_client.js:322:15)
    at Socket.socketOnEnd (_http_client.js:425:23)
    at Socket.emit (events.js:187:15)
    at endReadableNT (_stream_readable.js:1092:12)
    at process._tickCallback (internal/process/next_tick.js:63:19)
ERROR: Job failed: exit code 1

My gitlab-ci file:

image: tarampampam/node:10.10-alpine
    - ~/.npm
    - .jest
  - deploy
  - npm ci
  stage: deploy
    - npx expo login -u $EXPO_USERNAME -p $EXPO_PASSWORD
    - npx expo publish --non-interactive

Any thoughts on how to address this?

you might want to contact gitlab about it, it sounds like an issue with their allocation of disk space on their vms

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.