Make Scripts run within Screen #892

Closed
opened 2026-02-04 22:04:45 +03:00 by OVERLORD · 2 comments
Owner

Originally created by @Nerexbcd on GitHub (May 3, 2025).

🌟 Briefly describe the feature

Make Scripts Run within Screen to avoid accidental Script Interruption

📝 Detailed description

Make the scripts start inside a screen instance instead of the web connected terminal to avoid accidental interruption from browser to PVE.
This has been an issue for me since I usually work on mobile data, and internet is not as stable as I would like, resulting in disconnection from the PVE Console, and Interrupting the script mid run.
The Package I'm referring is Screen, that was used to be able to leave a software running without needing to have a remote terminal open (Like a Minecraft Server).

💡 Why is this useful?

Avoid Interruption of Scripts Mid Run leaving LXC container missconfigured or locked, or leaving softwares not completly installed.

Originally created by @Nerexbcd on GitHub (May 3, 2025). ### 🌟 Briefly describe the feature Make Scripts Run within Screen to avoid accidental Script Interruption ### 📝 Detailed description Make the scripts start inside a screen instance instead of the web connected terminal to avoid accidental interruption from browser to PVE. This has been an issue for me since I usually work on mobile data, and internet is not as stable as I would like, resulting in disconnection from the PVE Console, and Interrupting the script mid run. The Package I'm referring is [Screen](https://wiki.debian.org/screen), that was used to be able to leave a software running without needing to have a remote terminal open (Like a Minecraft Server). ### 💡 Why is this useful? Avoid Interruption of Scripts Mid Run leaving LXC container missconfigured or locked, or leaving softwares not completly installed.
OVERLORD added the enhancement label 2026-02-04 22:04:45 +03:00
Author
Owner

@MickLesk commented on GitHub (May 3, 2025):

Unfortunately, this is not possible as this is a crossover script procedure. The build.func and the install.func are required over several levels.

Unless I understand the request completely wrong.

The fact is: a local deployment is not possible because the scripts are not designed in this way and could never work in this way.

@MickLesk commented on GitHub (May 3, 2025): Unfortunately, this is not possible as this is a crossover script procedure. The build.func and the install.func are required over several levels. Unless I understand the request completely wrong. The fact is: a local deployment is not possible because the scripts are not designed in this way and could never work in this way.
Author
Owner

@Nerexbcd commented on GitHub (May 5, 2025):

I don't understand exacly how the scripts are structured, and because of it, @MickLesk, I didn't understood what the .func would have to do with this. But I'm just refering to executing a command on the terminal before the real script execution.

Because this is supposed to be just if the connection between the Browser and the PVE Instance fails, but the PVE Instance will always need internet access.

Usually I already do it manually, I made this Feature Request because as I sometimes have that issue, other people can also have it.

What I usually do to prevent script execution interruption:

$ screen
$ bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/xx/xxx.sh)"

The First command opens a new screen

And if I sudenly lose the connection of the Browser Remote Console of the PVE Instance:

$ screen -r

This command Recovers the last opened screen

@Nerexbcd commented on GitHub (May 5, 2025): I don't understand exacly how the scripts are structured, and because of it, @MickLesk, I didn't understood what the .func would have to do with this. But I'm just refering to executing a command on the terminal before the real script execution. Because this is supposed to be just if the connection between the Browser and the PVE Instance fails, but the PVE Instance will always need internet access. Usually I already do it manually, I made this Feature Request because as I sometimes have that issue, other people can also have it. ### What I usually do to prevent script execution interruption: ```bash $ screen $ bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/xx/xxx.sh)" ``` > The First command opens a new screen ### And if I sudenly lose the connection of the Browser Remote Console of the PVE Instance: ```bash $ screen -r ``` > This command Recovers the last opened screen
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#892