starred/ProxmoxVE

Fork 0

mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-04-26 01:36:05 +03:00

[GH-ISSUE #11046] Unable to install Jotty: ENOSPC Error #2365

New issue

Closed

opened 2026-02-26 12:52:12 +03:00 by kerem · 4 comments

kerem commented

2026-02-26 12:52:12 +03:00

Owner

Originally created by @miakela on GitHub (Jan 22, 2026).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/11046

✅ Have you read and understood the above guidelines?

yes

🔎 Did you run the script with verbose mode enabled?

Yes, verbose mode was enabled and the output is included below

📜 What is the name of the script you are using?

jotty

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/jotty.sh)"

⚙️ What settings are you using?

Default Settings
Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

9.1.1/42db4a6cf33dac83

📝 Provide a clear and concise description of the issue.

Couldn't get it to create a LXC - always failed because of lack of space. It worked by changing the disk size to 8, though.

🔄 Steps to reproduce the issue.

Step 1: run command unchanged
Step 2: Build failed with Error: ENOSPC

Step 3: Advanced Settings - Change Disk size to 8
Step 4: Build successful.

❌ Paste the full error output (if available).

Creating an optimized production build ...

[PWA] Compile server
[PWA] Compile server
[PWA] Compile client (static)
[PWA] Auto register service worker with: /opt/jotty/node_modules/next-pwa/register.js
[PWA] Service worker: /opt/jotty/public/sw.js
[PWA] url: /sw.js
[PWA] scope: /
[webpack.cache.PackFileCacheStrategy] Caching failed for pack: Error: ENOSPC: no space left on device, mkdir '/opt/jotty/.next/cache/webpack'
Failed to compile.

Error: ENOSPC: no space left on device, write

Build failed because of webpack errors
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

🖼️ Additional context (optional).

Checked available space beforehand, nothing is full, so excluded this possibility.

Originally created by @miakela on GitHub (Jan 22, 2026). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/11046 ### ✅ Have you read and understood the above guidelines? yes ### 🔎 Did you run the script with verbose mode enabled? Yes, verbose mode was enabled and the output is included below ### 📜 What is the name of the script you are using? jotty ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/jotty.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? 9.1.1/42db4a6cf33dac83 ### 📝 Provide a clear and concise description of the issue. Couldn't get it to create a LXC - always failed because of lack of space. It worked by changing the disk size to 8, though. ### 🔄 Steps to reproduce the issue. Step 1: run command unchanged Step 2: Build failed with Error: ENOSPC Step 3: Advanced Settings - Change Disk size to 8 Step 4: Build successful. ### ❌ Paste the full error output (if available). Creating an optimized production build ... > [PWA] Compile server > [PWA] Compile server > [PWA] Compile client (static) > [PWA] Auto register service worker with: /opt/jotty/node_modules/next-pwa/register.js > [PWA] Service worker: /opt/jotty/public/sw.js > [PWA] url: /sw.js > [PWA] scope: / <w> [webpack.cache.PackFileCacheStrategy] Caching failed for pack: Error: ENOSPC: no space left on device, mkdir '/opt/jotty/.next/cache/webpack' Failed to compile. Error: ENOSPC: no space left on device, write > Build failed because of webpack errors error Command failed with exit code 1. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. ### 🖼️ Additional context (optional). Checked available space beforehand, nothing is full, so excluded this possibility.

kerem

2026-02-26 12:52:12 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 12:52:13 +03:00

Author

Owner

@vhsdream commented on GitHub (Jan 22, 2026):

This app keeps getting hungrier and hungrier! I wonder if an alpine version would be a better fit?

@vhsdream commented on GitHub (Jan 22, 2026): This app keeps getting hungrier and hungrier! I wonder if an alpine version would be a better fit?

kerem commented

2026-02-26 12:52:13 +03:00

Author

Owner

@MickLesk commented on GitHub (Jan 22, 2026):

or an prebuild? @fccview can you tell a little bit more? its an 96% typescript app, so an prebuild should not a big deal and we can force 1-2gb RAM and less Disk. Its an simple github Action. Feel free, if you need help, to link me in an issue or discussion and i can fork it

@MickLesk commented on GitHub (Jan 22, 2026): or an prebuild? @fccview can you tell a little bit more? its an 96% typescript app, so an prebuild should not a big deal and we can force 1-2gb RAM and less Disk. Its an simple github Action. Feel free, if you need help, to link me in an issue or discussion and i can fork it

kerem commented

2026-02-26 12:52:13 +03:00

Author

Owner

@fccview commented on GitHub (Jan 22, 2026):

Hi, I am a bit confused by this.
The docker image (which IS based off alpine) is 300mb and uses 200mb of ram at most.

@MickLesk we created a variation of the script that should use standalone mode and shouldn't be bigger than 30mb in size.

When running this natively on my ubuntu/mac ram usage is never more than 200mb just like the docker image.

What am I missing here? Shall we get together and figure it out? I don't use proxmox, but the numbers I keep seeing here are absurd, no wonder it keeps failing >.>

edit

right, this is only in the install phase isn't it?

@fccview commented on GitHub (Jan 22, 2026): Hi, I am a bit confused by this. The docker image (which IS based off alpine) is 300mb and uses 200mb of ram at most. @MickLesk we created a variation of the script that should use standalone mode and shouldn't be bigger than 30mb in size. When running this natively on my ubuntu/mac ram usage is never more than 200mb just like the docker image. What am I missing here? Shall we get together and figure it out? I don't use proxmox, but the numbers I keep seeing here are absurd, no wonder it keeps failing >.> *edit* right, this is only in the install phase isn't it?

kerem commented

2026-02-26 12:52:13 +03:00

Author

Owner

@MickLesk commented on GitHub (Jan 22, 2026):

the only - what i see, its you use node20 (EOL), and we 22.
In this case is not the ram the limiting, the hdd isnt enough.

we do following;
cd /opt/jotty
unset NODE_OPTIONS
export NODE_OPTIONS="--max-old-space-size=3072"
yarn --frozen-lockfile
yarn next telemetry disable
yarn build

and you do;
yarn build

@MickLesk commented on GitHub (Jan 22, 2026): the only - what i see, its you use node20 (EOL), and we 22. In this case is not the ram the limiting, the hdd isnt enough. we do following; cd /opt/jotty unset NODE_OPTIONS export NODE_OPTIONS="--max-old-space-size=3072" yarn --frozen-lockfile yarn next telemetry disable yarn build and you do; yarn build

kerem referenced this issue

2026-02-26 13:34:28 +03:00

[PR #2365] [MERGED] [Github Action] Update CHANGELOG.md #3727

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/ProxmoxVE#2365

No description provided.

Rows
Columns