[PR #10449] [MERGED] Increase BentoPDF RAM requirement from 2GB to 4GB #8756

Closed
opened 2026-02-26 16:33:59 +03:00 by kerem · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/community-scripts/ProxmoxVE/pull/10449
Author: @Copilot
Created: 12/31/2025
Status: Merged
Merged: 12/31/2025
Merged by: @MickLesk

Base: mainHead: copilot/fix-bentopdf-update-issue


📝 Commits (3)

📊 Changes

5 files changed (+5 additions, -5 deletions)

View changed files

📝 ct/bentopdf.sh (+1 -1)
📝 ct/convertx.sh (+1 -1)
📝 frontend/public/json/bentopdf.json (+1 -1)
📝 frontend/public/json/convertx.json (+1 -1)
📝 install/convertx-install.sh (+1 -1)

📄 Description

✍️ Description

BentoPDF's npm build process exhausts 2GB RAM during installation and updates, causing LXC crashes. Increased default allocation to 4GB, consistent with similar build-intensive scripts (changedetection, ghostfolio, reactive-resume, etc.).

Changes:

  • ct/bentopdf.sh: var_ram 2048 → 4096
  • frontend/public/json/bentopdf.json: ram 2048 → 4096

Prerequisites (X in brackets)

  • Self-review completed – Code follows project standards.
  • Tested thoroughly – Changes work as expected.
  • No security risks – No hardcoded secrets, unnecessary privilege escalations, or permission issues.

🛠️ Type of Change (X in brackets)

  • 🐞 Bug fix – Resolves an issue without breaking functionality.
  • New feature – Adds new, non-breaking functionality.
  • 💥 Breaking change – Alters existing functionality in a way that may require updates.
  • 🆕 New script – A fully functional and tested script or script set.
  • 🌍 Website update – Changes to website-related JSON files or metadata.
  • 🔧 Refactoring / Code Cleanup – Improves readability or maintainability without changing functionality.
  • 📝 Documentation update – Changes to README, AppName.md, CONTRIBUTING.md, or other docs.
Original prompt

This section details on the original issue you should resolve

<issue_title>Updating BentoPDF to 1.15.X fails</issue_title>
<issue_description>### 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?

BentoPDF

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

update

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

📝 Provide a clear and concise description of the issue.

When running the update the lxc with the default RAM of 2GB crashes. The same happens when doing a fresh install. The LXC runs of out memory.

🔄 Steps to reproduce the issue.

just update or install BentoPDF

Paste the full error output (if available).

LXC is not responsive anymore.

🖼️ Additional context (optional).

The fix is to increase the RAM from 2 to 4 GB for installation or the update process.</issue_description>

Comments on the Issue (you are @copilot in this section)


Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/community-scripts/ProxmoxVE/pull/10449 **Author:** [@Copilot](https://github.com/apps/copilot-swe-agent) **Created:** 12/31/2025 **Status:** ✅ Merged **Merged:** 12/31/2025 **Merged by:** [@MickLesk](https://github.com/MickLesk) **Base:** `main` ← **Head:** `copilot/fix-bentopdf-update-issue` --- ### 📝 Commits (3) - [`06895b6`](https://github.com/community-scripts/ProxmoxVE/commit/06895b67c4441223915cae335ed3ba4c588f4bf2) Initial plan - [`a871f4e`](https://github.com/community-scripts/ProxmoxVE/commit/a871f4eaad0af37f7dce59e635b83995634e5566) Increase BentoPDF RAM requirement from 2GB to 4GB - [`44f8e38`](https://github.com/community-scripts/ProxmoxVE/commit/44f8e38fa771c250f46039b739eed1a3d839f238) Bump ConvertX to Debian 13 (#10450) ### 📊 Changes **5 files changed** (+5 additions, -5 deletions) <details> <summary>View changed files</summary> 📝 `ct/bentopdf.sh` (+1 -1) 📝 `ct/convertx.sh` (+1 -1) 📝 `frontend/public/json/bentopdf.json` (+1 -1) 📝 `frontend/public/json/convertx.json` (+1 -1) 📝 `install/convertx-install.sh` (+1 -1) </details> ### 📄 Description ## ✍️ Description BentoPDF's npm build process exhausts 2GB RAM during installation and updates, causing LXC crashes. Increased default allocation to 4GB, consistent with similar build-intensive scripts (changedetection, ghostfolio, reactive-resume, etc.). **Changes:** - `ct/bentopdf.sh`: `var_ram` 2048 → 4096 - `frontend/public/json/bentopdf.json`: `ram` 2048 → 4096 ## ✅ Prerequisites (**X** in brackets) - [x] **Self-review completed** – Code follows project standards. - [x] **Tested thoroughly** – Changes work as expected. - [x] **No security risks** – No hardcoded secrets, unnecessary privilege escalations, or permission issues. --- ## 🛠️ Type of Change (**X** in brackets) - [x] 🐞 **Bug fix** – Resolves an issue without breaking functionality. - [ ] ✨ **New feature** – Adds new, non-breaking functionality. - [ ] 💥 **Breaking change** – Alters existing functionality in a way that may require updates. - [ ] 🆕 **New script** – A fully functional and tested script or script set. - [ ] 🌍 **Website update** – Changes to website-related JSON files or metadata. - [ ] 🔧 **Refactoring / Code Cleanup** – Improves readability or maintainability without changing functionality. - [ ] 📝 **Documentation update** – Changes to `README`, `AppName.md`, `CONTRIBUTING.md`, or other docs. <!-- START COPILOT ORIGINAL PROMPT --> <details> <summary>Original prompt</summary> > > ---- > > *This section details on the original issue you should resolve* > > <issue_title>Updating BentoPDF to 1.15.X fails</issue_title> > <issue_description>### ✅ 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? > > BentoPDF > > ### 📂 What was the exact command used to execute the script? > > update > > ### ⚙️ 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.4 > > ### 📝 Provide a clear and concise description of the issue. > > When running the update the lxc with the default RAM of 2GB crashes. The same happens when doing a fresh install. The LXC runs of out memory. > > ### 🔄 Steps to reproduce the issue. > > just update or install BentoPDF > > ### ❌ Paste the full error output (if available). > > LXC is not responsive anymore. > > ### 🖼️ Additional context (optional). > > The fix is to increase the RAM from 2 to 4 GB for installation or the update process.</issue_description> > > ## Comments on the Issue (you are @copilot in this section) > > <comments> > </comments> > </details> <!-- START COPILOT CODING AGENT SUFFIX --> - Fixes community-scripts/ProxmoxVE#10427 <!-- START COPILOT CODING AGENT TIPS --> --- ✨ Let Copilot coding agent [set things up for you](https://github.com/community-scripts/ProxmoxVE/issues/new?title=✨+Set+up+Copilot+instructions&body=Configure%20instructions%20for%20this%20repository%20as%20documented%20in%20%5BBest%20practices%20for%20Copilot%20coding%20agent%20in%20your%20repository%5D%28https://gh.io/copilot-coding-agent-tips%29%2E%0A%0A%3COnboard%20this%20repo%3E&assignees=copilot) — coding agent works faster and does higher quality work when set up for your repo. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
kerem 2026-02-26 16:33:59 +03:00
Sign in to join this conversation.
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#8756
No description provided.