search

vercel / pkg

Package your Node.js project into an executable
https://npmjs.com/pkg
MIT License
24.28k stars 1.01k forks source link

Error: ENOSPC: no space left on device, mkdtemp '/tmp/pkg-XXXXXX' #1990

Closed charbelMat closed 9 months ago

charbelMat commented 1 year ago

What version of pkg are you using?

5.8.1

What version of Node.js are you using?

16.20.1

What operating system are you using?

Ubuntu 22.04.1 LTS

What CPU architecture are you using?

x86_64

What Node versions, OSs and CPU architectures are you building for?

node16-linux-x64

Describe the Bug

When we run the binary on different Threads, 12 in our case on a 16 CPU machine, the /tmp folder is filled with pkg-XXXXX files and getting this memory error:

Error: ENOSPC: no space left on device, mkdtemp '/tmp/pkg-XXXXXX'

Our tmp storage is small (20 M approx) and we can't increase so is there's any way to change where pkg saves those files ?

Thank you

Expected Behavior

Use a different Directory than /tmp

To Reproduce

Run the built binary on different threads with a small tmp storage folder.

robertsLando commented 1 year ago

You should try opening a PR to set a different tmp folder using an env var. Remember to update docs too

charbelMat commented 1 year ago

thank you @robertsLando for your advice. but our cloud team won't let use modify the moutings.

robertsLando commented 1 year ago

What I mean is to create the PR on this project to add that funcitonality

charbelMat commented 1 year ago

It would be a pleasure to contribute. But first you have to explain to me what do u mean by PR :) And is there's any git standards to follow for contribution here ? Thank you

robertsLando commented 1 year ago

PR stays for pull request. It's a way to contribute to a git project. You essentially need to fork this project and start making the changes needed on that fork then you create a pull request once you are done, I will review your changes and if everything is ok merge them in master.

github-actions[bot] commented 9 months ago

This issue is stale because it has been open 90 days with no activity. Remove the stale label or comment or this will be closed in 5 days. To ignore this issue entirely you can add the no-stale label

github-actions[bot] commented 9 months ago

This issue is now closed due to inactivity, you can of course reopen or reference this issue if you see fit.