[rcourtman]

✍️ Description

The fix asked about on #212, and my last PR for a while, I promise 🙂

lib/forge.func staged release downloads and their extraction with mktemp -d, so in /tmp. On Debian 13 that is a tmpfs, so the staged release counts against the container's memory limit, and without swap nothing can reclaim it. Pulse's 273 MiB release unpacks to 725 MiB, so at its default 1 GB an update stalls or is OOM-killed.

The six staging sites now use _forge_workdir, which creates the directory under ${TMPDIR:-/var/tmp} and falls back to /tmp. That puts staging back on disk, where it was on Debian 12. Small metadata files stay in /tmp.

Tested with ct/pulse.sh at the default 1024 MiB, updating 6.6.0 to 6.7.0:

Case	main (48041b4)	This branch
Proxmox VE 9.2, default swap, install	–	passes
Proxmox VE 9.2, swap 0, update	stalls at 1023 MiB with 974 MiB in tmpfs	passes, tmpfs peak 4 MiB
Incus 6.0.4, no swap, install	–	passes
Incus 6.0.4, no swap, update	OOM-killed, service left stopped, 983 MiB left in /tmp	passes, tmpfs peak 4 MiB

The new tests in tests/forge-clean-install.sh fail on main. All tests pass, and ShellCheck reports nothing new.

🔗 Related Issue

Related: #212

✅ Prerequisites (X in brackets)

• Self-review completed – Code follows project standards.
• Tested thoroughly – Changes work as expected (Proxmox VE and/or Incus, as applicable).
• No security risks – No hardcoded secrets, unnecessary privilege escalations, or permission issues.
• API.txt regenerated – If a function signature or behavior changed, API.txt was updated to match.

---

🛠️ 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 behavior in a way that may require updates in every downstream script.
• 🔧 Refactoring / Code Cleanup – Improves readability or maintainability without changing functionality.
• 📝 Documentation update – Changes to README, docs/, CONTRIBUTING.md, or other docs.

---

🤖 AI Assistance (X in brackets)

If you used an AI tool (GitHub Copilot, Claude, ChatGPT, etc.) to write or generate any code in this PR, you must confirm compliance below.
Select exactly one option.

• No AI used – Code was written without AI assistance.
• AI was used – The output has been reviewed and corrected, and I take responsibility for it matching this repo's conventions.

[github-actions]

Try this branch

The engine and the scripts resolve independently, so a production script can
be run against the engine from this PR by setting one variable:

COMMUNITY_SCRIPTS_CORE_URL=https://raw.githubusercontent.com/rcourtman/core/fix/stage-releases-on-disk \
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/debian.sh)"

Swap ct/debian.sh for whatever exercises the change.

Run a script from a fork as well

curl -fsSL https://raw.githubusercontent.com/rcourtman/core/fix/stage-releases-on-disk/tools/run.sh |
  bash -s -- https://raw.githubusercontent.com/YOU/DevScripts/your-branch ct/debian.sh \
             https://raw.githubusercontent.com/rcourtman/core/fix/stage-releases-on-disk

Note that run.sh is reached through a pipe, so the script it starts inherits
an exhausted stdin. Whiptail is fine — it opens /dev/tty — but a plain read
would see EOF. The single-variable form above does not have that problem.

Useful flags while testing

dev_mode=net logs every engine fetch with status and duration, which is the
quickest way to confirm the branch is really being used. dev_mode=keep stops a
failed build from deleting the container along with the evidence.