markmorado/pvemanager
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 3 Wiki Activity

fix: set 755 permissions on pve CLI so non-root users can read the script
Some checks failed
Deploy to Production / Trigger production update (push) Failing after 10s
Details

Browse Source 
sudo cp preserves the source umask which can leave the file without
read permission for group/others.  A bash script needs both read and
execute bits — without read, the shell cannot interpret it.
This commit is contained in:
Dilshod Rasulov
2026-08-17 01:20:43 +05:00
parent a275b8bed5
commit 820da8ca01
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
deploy.sh
View File

@@ -1053,7 +1053,7 @@ install_pve_cli() {
print_error "Не удалось подготовить pve CLI" print_error "Не удалось подготовить pve CLI"
return 1 return 1
fi fi
chmod +x "$tmp_cli" chmod 755 "$tmp_cli"
# Try to install to /usr/local/bin (global PATH) # Try to install to /usr/local/bin (global PATH)
local installed=false local installed=false
@@ -1062,7 +1062,7 @@ install_pve_cli() {
else else
# Not root — try sudo (password may already be cached from docker ops) # Not root — try sudo (password may already be cached from docker ops)
if sudo cp "$tmp_cli" "$install_path" 2>/dev/null && \ if sudo cp "$tmp_cli" "$install_path" 2>/dev/null && \
sudo chmod +x "$install_path" 2>/dev/null; then sudo chmod 755 "$install_path" 2>/dev/null; then
installed=true installed=true
fi fi
fi fi