e80241745f
Previously, when a container was stopped or base package installation failed during 'Customizing LXC Container', the error handler's simple 'Remove broken container? (Y/n)' prompt appeared instead of the full recovery menu with retry/repair options (verbose rebuild, APT repair, OOM retry, DNS override). Root cause: set -Eeuo pipefail and ERR trap were still active during the customization phase (locale, timezone, base packages). The exit 1 triggered error_handler() which has its own cleanup flow, bypassing the full recovery menu in build_container(). Changes: - Disable ERR trap before customization phase (not just before lxc-attach) - Replace exit 1 with install_exit_code=1 for base package failures - Wrap lxc-attach section in if-block that skips when customization failed - Both customization and install errors now reach the full recovery menu - Fix read in error_handler.func to use </dev/tty (same curl stdin issue) - Eliminates 'pop_var_context: head of shell_variables not a function context' bash error caused by double-exit (exit 1 -> ERR trap -> exit)
Proxmox VE Helper-Scripts
A Community Legacy in Memory of @tteck
Simplify your Proxmox VE setup with community-driven automation scripts
Originally created by tteck, now maintained and expanded by the community
🎯 Key Features
⚡ Quick SetupOne-command installations for popular services and containers |
⚙️ Flexible ConfigSimple mode for beginners, advanced options for power users |
🔄 Auto UpdatesKeep your installations current with built-in update mechanisms |
🛠️ Easy ManagementPost-install scripts for configuration and troubleshooting |
👥 Community DrivenActively maintained with contributions from users worldwide |
📖 Well DocumentedComprehensive guides and community support |
🔒 SecureRegular security updates and best practices |
⚡ PerformanceOptimized configurations for best performance |
📋 Requirements
🖥️ Proxmox VEVersion: 8.4.x | 9.0.x | 9.1.x |
🐧 Operating SystemDebian-based with Proxmox Tools |
🌐 NetworkInternet connection required |
📥 Getting Started
Choose your preferred installation method:
Method 1: One-Click Web Installer
The fastest way to get started:
- Visit helper-scripts.com 🌐
- Search for your desired script (e.g., "Home Assistant", "Docker")
- Copy the bash command displayed on the script page
- Open your Proxmox Shell and paste the command
- Press Enter and follow the interactive prompts
Method 2: PVEScripts-Local
Install a convenient script manager directly in your Proxmox UI:
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/pve-scripts-local.sh)"
This adds a menu to your Proxmox interface for easy script access without visiting the website.
📖 Learn more: ProxmoxVE-Local Repository
💬 Join the Community
💬 DiscordReal-time chat, support, and discussions 
|
💭 DiscussionsFeature requests, Q&A, and ideas 
|
🐛 IssuesBug reports and issue tracking 
|
🛠️ Contribute
💻 CodeAdd new scripts or improve existing ones |
📝 DocumentationWrite guides, improve READMEs, translate content |
🧪 TestingTest scripts and report compatibility issues |
💡 IdeasSuggest features or workflow improvements |
👉 Check our Contributing Guidelines to get started
❤️ Support the Project
This project is maintained by volunteers in memory of tteck. Your support helps us maintain infrastructure, improve documentation, and give back to important causes.
🎗️ 30% of all donations go directly to cancer research and hospice care
Every contribution helps keep this project alive and supports meaningful causes
📈 Project Statistics
📜 License
This project is licensed under the MIT License - feel free to use, modify, and distribute.
Proxmox® is a registered trademark of Proxmox Server Solutions GmbH