starred/ProxmoxVE

Fork 0

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

[GH-ISSUE #10117] Jotty update requires additional disk space at each update #2190

New issue

Closed

opened 2026-02-26 12:51:36 +03:00 by kerem · 7 comments

kerem commented

2026-02-26 12:51:36 +03:00

Owner

Originally created by @hrglzpf on GitHub (Dec 18, 2025).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/10117

Originally assigned to: @vhsdream on GitHub.

✅ 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?

the one that is executed when i use the "update" func inside the LXC container

⚙️ 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

📝 Provide a clear and concise description of the issue.

At every update the required disk space increases.
Actual case: Jotty 1.13.1 --> 1.14 increases disk size of the container from 6.7G to 8.5G

🔄 Steps to reproduce the issue.

update Jotty using the "update" command in the container´s shell.

❌ Paste the full error output (if available).

No error output

🖼️ Additional context (optional).

Is there any "manual" deletion of leftovers possible - would be a workaround for me

Originally created by @hrglzpf on GitHub (Dec 18, 2025). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/10117 Originally assigned to: @vhsdream on GitHub. ### ✅ 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? the one that is executed when i use the "update" func inside the LXC container ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? 9.1 ### 📝 Provide a clear and concise description of the issue. At every update the required disk space increases. Actual case: Jotty 1.13.1 --> 1.14 increases disk size of the container from 6.7G to 8.5G ### 🔄 Steps to reproduce the issue. update Jotty using the "update" command in the container´s shell. ### ❌ Paste the full error output (if available). No error output ### 🖼️ Additional context (optional). Is there any "manual" deletion of leftovers possible - would be a workaround for me

kerem

2026-02-26 12:51:36 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 12:51:37 +03:00

Author

Owner

@vhsdream commented on GitHub (Dec 18, 2025):

Yeah I've noticed, not to mention that it requires 4GB of RAM in order to not crash during update.

It uses yarn as a package manager, so I'm not sure if the cleanup function in the update script covers that use case.

Perhaps I can add a yarn cache clean in the meantime. @MickLesk is yarn covered in the cleanup function?

@vhsdream commented on GitHub (Dec 18, 2025): Yeah I've noticed, not to mention that it requires 4GB of RAM in order to not crash during update. It uses yarn as a package manager, so I'm not sure if the cleanup function in the update script covers that use case. Perhaps I can add a `yarn cache clean` in the meantime. @MickLesk is yarn covered in the cleanup function?

kerem commented

2026-02-26 12:51:37 +03:00

Author

Owner

@MickLesk commented on GitHub (Dec 18, 2025):

Yes, should be, If its Not enough feel free to add it in core.func

@MickLesk commented on GitHub (Dec 18, 2025): Yes, should be, If its Not enough feel free to add it in core.func

kerem commented

2026-02-26 12:51:37 +03:00

Author

Owner

@hrglzpf commented on GitHub (Dec 18, 2025):

Can I try something?
My backups are working, so it´s not risky at all 😄

@hrglzpf commented on GitHub (Dec 18, 2025): Can I try something? My backups are working, so it´s not risky at all 😄

kerem commented

2026-02-26 12:51:37 +03:00

Author

Owner

@vhsdream commented on GitHub (Dec 18, 2025):

Yeah, note disk usage before, then run yarn cache clean in the LXC and check disk usage again.

I had to do this yesterday, and I went from 3.99 GB to 1.6 GB.

@vhsdream commented on GitHub (Dec 18, 2025): Yeah, note disk usage before, then run `yarn cache clean` in the LXC and check disk usage again. I had to do this yesterday, and I went from 3.99 GB to 1.6 GB.

kerem commented

2026-02-26 12:51:37 +03:00

Author

Owner

@hrglzpf commented on GitHub (Dec 18, 2025):

Done
Went down from 8.5G to 4.54G

@hrglzpf commented on GitHub (Dec 18, 2025): Done Went down from 8.5G to 4.54G

kerem commented

2026-02-26 12:51:37 +03:00

Author

Owner

@vhsdream commented on GitHub (Dec 18, 2025):

@MickLesk The cleanup_lxc function isn't typically run in the update script, right? It should be OK to run it before grabbing the update I think. Opposed to me adding it to the jotty script?

@vhsdream commented on GitHub (Dec 18, 2025): @MickLesk The `cleanup_lxc` function isn't typically run in the update script, right? It should be OK to run it before grabbing the update I think. Opposed to me adding it to the jotty script?

kerem commented

2026-02-26 12:51:37 +03:00

Author

Owner

@vhsdream commented on GitHub (Dec 18, 2025):

I just had the build fail when I tested the update. I'll need to make sure it wasn't caused by the cleanup_lxc before moving ahead.

@vhsdream commented on GitHub (Dec 18, 2025): I just had the build fail when I tested the update. I'll need to make sure it wasn't caused by the cleanup_lxc before moving ahead.

kerem referenced this issue

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

[PR #2191] [MERGED] Fix: "read -p" does not support color formatting #3596

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#2190

No description provided.

Rows
Columns