PVE LXC Execute Command
PVE LXC Execute Command is a set of shell scripts for Proxmox VE that run a single command inside one LXC container, or across all running containers at once.
Platform availability
Available on 1 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
50/100 Fair
- Maintained
- 64last commit 109 days ago
- Popular
- 3662 GitHub stars
- Easy to install
- 150 install platforms, install notes
- Light to run
- No data
- Security check
- 75no serious findings
Based on 4 of 5 factors.
- GitHub stars
- 62
- Open issues
- 1
- Last commit
- 2026-08-04
- License
- MIT
- Activity
- stale
Checked 3 days ago - source: GitHub (morph027/pve-lxc-scripts)
Resources & Compatibility
Requirements not published yet.
First-install notes
- Add the PVE driver to Rancher Use the Helm commands to fetch and install the Proxmox VE node driver and its UI extension, and set PVE_NODE_DRIVER_VERSION to a real released version first. Without this, Rancher won’t know how to talk to your Proxmox servers. source
- Rancher offline? Use local file URLs If your Rancher server can’t reach the internet, set nodeDriver.url and uiPlugin.endpoint to copies of the driver and UI extension hosted somewhere Rancher can reach. This stops the install from failing because Rancher can’t download the files. source
- Using the scripts Use lxc-exec <ctid> <command> to run a command in a specific container (e.g. lxc-exec 1337 apt-get update); lxc-exec-all <command> targets every running container, and lxc-update-all updates software on all running apt-get or yum containers. source
Fetched 42 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Does PVE LXC Execute Command start stopped containers?
If a container is stopped, the script automatically starts it and then runs the command.
Can I exclude specific containers from a command run?
Containers can be selectively excluded using an interactive checklist.
Answers sourced from proxmox-scripts.com
Community
- Run command in container at startup : r/Proxmox - Reddit (reddit)
- Is there a way to execute a post vm/lxc instantiation script - Reddit (reddit)
- Proxmox execute command - Proxmox Support Forum (forum)
- How do you provision LCX with ansible : r/Proxmox - Reddit (reddit)
- Executing a command inside a running LXC - Unix & Linux Stack Exchange (forum)
Collected 48 days ago - public community threads