❗️Help Wanted: Debugging “Unknown error, exit code: 1” in create_lxc.sh

[MickLesk]

🧩 Problem Summary

We’re encountering a frequent issue during the automated LXC creation process in create_lxc.sh used by community-scripts/ProxmoxVE.

The script exits with:

Unknown error, exit code: 1 in create_lxc.sh

This error appears 100–200 times per day across community installations and remains difficult to reproduce consistently in a controlled environment.

---

🔍 What I’m Looking For

I need help understanding what exactly causes this exit code 1, especially since:

• Some issues have already been fixed (template availability, default storages, cluster quorum false-positives)
• But this specific exit still occurs intermittently, even with the latest patches applied

---

📋 What You Can Do to Help

Please share the full console output during the failing run:

🔧 From the beginning of the installation process until the point where the error occurs.

---

💡 Additional Context

• Script: create_lxc.sh
• Triggered by: build.func → create_lxc.sh
• Environment: Proxmox VE 8 → mostly Debian/Ubuntu containers
• Error Rate: 100–200 times/day (as observed via telemetry and support)

---

✅ Known Causes Already Fixed

• Invalid/missing LXC templates
• Broken DNS/network check
• Quorum check failure on single-node setups
• Missing default pool/storage handling

---

🤝 Let’s Fix This Together

Any logs, patterns, error messages, or even vague suspicions are highly appreciated.
The goal is to improve script robustness and eliminate this unknown exit path.

Thanks in advance!
— MickLesk @ community-scripts

[MickLesk]

Part 1 - found an issue with quorum of Cluster

#5278

Part 2 - found an issue with not rfc1123 hostnames | check recursive integer values (DISK_SIZE,CORE_COUNT,RAM_SIZE)
#5291