Replies: 16 comments 21 replies
-
|
If you test it for one OS then it's the one to be used. Any other OS can be used but then you are on your own. You know the risk! |
Beta Was this translation helpful? Give feedback.
-
|
If we did keep it, could we have either the default more clearly labeled or the alternative options be clearly labeled as unsupported? I am always second guessing myself when deciding which version to press. |
Beta Was this translation helpful? Give feedback.
-
|
Remark: The Default OS and Version are already pre-selected since some weeks. |
Beta Was this translation helpful? Give feedback.
-
|
Be like Henry Ford: you can have any color you want, as long as it's black |
Beta Was this translation helpful? Give feedback.
-
|
I think keep it, so that it motivates people to develop the other OS more. I know I would like a Centos/RHEL rpm option if one becomes available. |
Beta Was this translation helpful? Give feedback.
-
|
Maybe as Single lxc, but not as fully available Option. Ive already opensuse, rpm based LXC's in my private dev. Work smooth, but its only for experts |
Beta Was this translation helpful? Give feedback.
-
|
I'd like top keep it but clearly lable hat if that option is used. users are on their own. |
Beta Was this translation helpful? Give feedback.
-
|
for example? Maybe an additional Dialogue? The Header is clear (i think), but many people ignore the header 🫠 |
Beta Was this translation helpful? Give feedback.
-
|
Remove it. |
Beta Was this translation helpful? Give feedback.
-
|
I've always picked Debian 12 even when not default, to keep my Proxmox uniform. I've selected to remove the option to hopefully reduce the issues for others and improve stability. However I'd love to see a world where we have multiple supported OS for applications. |
Beta Was this translation helpful? Give feedback.
-
|
Removing the Option will certainly reduce the number of issues. And i like the idea for support for all OSes, but this is so much work, and would be a nightmare to maintain. And some Apps, like Homeassistant Core support only Ubuntu 24.10. |
Beta Was this translation helpful? Give feedback.
-
|
Maybe logging installation details in the 'content' field (or txt file) of the LXC which need to be supplied when asking for help? |
Beta Was this translation helpful? Give feedback.
-
|
It should never take away the pleasure.. Isn't the responsibility taken too seriously? No offense.. but it is all for free without a professional desk system. How many people does the group consist of anyway? |
Beta Was this translation helpful? Give feedback.
-
|
Currently i work on a docs site, But from the experience of the last few months, it is consistently ignored. The issue template also says that you should search before an issue (example python3 error, certainly 50 issues on this topic but the solution can be found directly as a guide) |
Beta Was this translation helpful? Give feedback.
-
Do you mean our Contributors? Currently 6 Main Contributor and 16 "scripter" |
Beta Was this translation helpful? Give feedback.
-
|
.. That is rather serious. It should not affect happiness. |
Beta Was this translation helpful? Give feedback.
-
|
Well, it's not bad. It's more the ignorance or what I call "attacks" due to the attitude that are sobering. You always have to act correctly and ultimately close the issue, which sometimes creates a shitstorm. |
Beta Was this translation helpful? Give feedback.
-
|
So long as the Alpine offerings continue to exist (separate of course) for those wanting the absolute bare minimum setup, I see no reason to support alternate OS configurations. |
Beta Was this translation helpful? Give feedback.
-
|
Alpine will of course remain as optional script and may be extended by a few more scripts in next time. It's purely about Debian <--> Ubuntu |
Beta Was this translation helpful? Give feedback.
-
|
I would probably leave the pull running until the end of March. We would still like to hear opinions. We will then present the final solution/idea as soon as possible. |
Beta Was this translation helpful? Give feedback.
-
|
Is it possible to remove it, but just to the extent of commenting it out on the scripts? |
Beta Was this translation helpful? Give feedback.
-
|
I like the idea of giving advanced users a way of using it without exposing to all |
Beta Was this translation helpful? Give feedback.
-
|
The OS is determined in the APP.sh script part. Even if we remove the OS Option, you can always edit the os in the file however you like it. |
Beta Was this translation helpful? Give feedback.
-
|
I feel like if someone is advanced enough to want this, they should have no issue editing the script to make it happen. |
Beta Was this translation helpful? Give feedback.
-
|
As long as the LXC script works I don't care (in a good way) which OS is running behind. So if is helps for maintainability to remove unsupported OS's I'm okay with it. |
Beta Was this translation helpful? Give feedback.
-
|
I'd prefer keeping the selection, but fix the scripts so that they work with both OS types (in case it is possible to use both). Surely this takes time and ressources, but I think it's worth it. |
Beta Was this translation helpful? Give feedback.
-
|
This would be a huge amount of work for 310+ Scripts, and we agreed to only use Debian 12 if possible. |
Beta Was this translation helpful? Give feedback.
-
|
I am currently experimenting with the following function: var_os=“ubuntu” var_version=“24.10” var_cpu=“2” var_ram=“1024” bash -c “$(curl -fsSL https://github.com/community-scripts/ProxmoxVED/raw/main/ct/debian.sh)” This makes it possible for Pro users to select a different OS specifically for scripts. If bugs still come in, they will still be rejected. Everyone can feel free to contribute to the project and start bugfixes (e.g. lsb-release for repos or similar). This way we can remove it from the dialog for “more unknowing” users, and the “hardcore” user can still try it this way. |
Beta Was this translation helpful? Give feedback.
-
|
I think that's perfect |
Beta Was this translation helpful? Give feedback.
-
|
Why not use those existing variables within the scripts themselfs (I'm sure that would fix many of the apt repo issues) and use a flag like |
Beta Was this translation helpful? Give feedback.
-
|
idk what you mean. Do an PR in VED and we take an look |
Beta Was this translation helpful? Give feedback.
-
|
@MickLesk sorry, I've been busy at work that. I thought aber something like this: bash -c “$(curl -fsSL https://github.com/community-scripts/ProxmoxVED/raw/main/ct/debian.sh)”runs through the default script settings without any selections (except the script need additional data like api key, credentials, …) In case you definitely want to force an extra step for using different settings for "pro users", one could use bash -c “$(curl -fsSL https://github.com/community-scripts/ProxmoxVED/raw/main/ct/debian.sh)” --advancedin order to re-enable the OS selection and dialogs for container settings. Additionally you could pre-define variables to override the default settings (and use the default values for parameters that are not set via script-call) in a way like bash -c “$(curl -fsSL https://github.com/community-scripts/ProxmoxVED/raw/main/ct/debian.sh)” --override os=ubuntu version='24.04'The main question for this would be how to maintain the scripts using three different possibilities to run them. Does this make it easier to understand my thoughts? 😅 |
Beta Was this translation helpful? Give feedback.
-
|
It makes it easier to understand, but this would compicate things a fair bit to parse command line params. Micks aproach is much more simple. And only a minor chnge is needed. |
Beta Was this translation helpful? Give feedback.
-
|
Merged with PR #3771 |
Beta Was this translation helpful? Give feedback.
-
🗳️ Community Poll: OS/Version Selection in Advanced Settings
📢 Should We Keep the OS/Version Selection?
Currently, in the Advanced Settings, users can select a different OS or version than the officially supported one.
For example, if a script is designed for Ubuntu 22.04, a user can still choose Debian 12.
🔹 This may work, but it is not officially supported, and issues may arise.
🔹 Our official support is limited to the default OS for each script.
A significant number of reported issues are caused by users selecting unsupported OS versions.
Even though the correct OS is pre-selected and the limitations are clearly stated in the OS selection UI,
we frequently have to explain and discuss why certain errors occur.
Additionally, our Issue Template clearly states that support is provided only for the default OS/version,
yet we still receive reports from users who choose alternative configurations and expect full support.
🏗️ We Need Your Feedback!
Should we:
✅ Keep the OS/Version selection – Users can continue to select custom OS versions at their own risk.
❌ Remove the OS/Version selection – Only officially supported OS versions will be available.
Let us know what you think by voting in this poll! 🗳️
Community Scripts ORG Team
221 votes ·
Beta Was this translation helpful? Give feedback.
All reactions