Creating a cron job that routinely pulls a script from the Internet and runs it as root is... not a great idea

[TFenby]

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

cron-update-lxcs.sh

📂 What was the exact command used to execute the script?

n/a

⚙️ What settings are you using?

• Default Settings
• Advanced Settings

🖥️ Which Linux distribution are you using?

No response

📝 Provide a clear and concise description of the issue.

As the title says, the current cron-update-lxcs.sh is a security nightmare waiting to happen. At most, the version of update-lxcs-cron.sh currently published should be downloaded and cached locally.

🔄 Steps to reproduce the issue.

n/a

❌ Paste the full error output (if available).

n/a

🖼️ Additional context (optional).

n/a

[MickLesk]

Then make a sensible suggestion 🤷🏼‍♂️

The only solution would be that
you would have to install a shell script on each LXC, which always has exactly the same name, so that the Proxmox host can address it. Everything must be callable via PCT. This is not worth the huge effort, and whether it works properly at all is another question. If you don't like the script - as with all other scripts in the repo - you don't have to use it.

By the way, LXCs are always root.