Tools & Add-onsPVE Tools
PVE Update Repositories
Point the update command of older containers from tteck/Proxmox to community-scripts/ProxmoxVE.
Containers created before the project moved carry a /usr/bin/update that downloads from tteck/Proxmox. update-repo.sh rewrites that file in every Debian and Ubuntu container so that update uses community-scripts/ProxmoxVE.
Website entry: update-repo. Source: tools/pve/update-repo.sh.
Run
In the Proxmox VE host shell, as root:
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/tools/pve/update-repo.sh)"There are no prompts. The script starts working on all containers immediately.
What it does
For each container from pct list with ostype debian or ubuntu it checks /usr/bin/update through pct exec:
State of /usr/bin/update | Output | Action |
|---|---|---|
Contains community-scripts/ProxmoxVE | [No Change] | None. |
Has at least one line without tteck | [Warning] ... contains a different entry | None. |
| Otherwise | [Success] or [Error] | sed -i 's/tteck\/Proxmox/community-scripts\/ProxmoxVE/g' /usr/bin/update |
| File missing | [Error] /usr/bin/update not found | None. |
Containers with another OS type are skipped with (not Debian/Ubuntu).
Environment variables
| Variable | Default | Purpose |
|---|---|---|
COMMUNITY_SCRIPTS_CORE_URL | https://raw.githubusercontent.com/community-scripts/core/main | Base URL the script loads api/api.func from. |
Limits
- The script does not start stopped containers.
pct execfails on them, so they are reported as/usr/bin/update not found. Start the containers you want to convert first. - There is no undo and no backup of the old file.
- The final message says the repositories were switched even if no file was changed. Read the per-container lines.