Hi,
I have an interest in providing linux containers to other users, restricting their access only to what they need to manage their owned container(s). To my surprise I have found one glaring hole in the feature-set - an ability to reinstall the OS for a given container. Looking at the API and user privileges, the closest thing to this is deleting and recreating the container but that can't be restrained to any useful scope e.g. allow a user to only "own" a limited number of CT's (they cannot create more than that number).
I haven't worked on PHP or JS for about a decade and have barely touched the Perl language (I am a Java and C# developer by trade) but I'd be willing to dive in and try to take a crack at adding a button and privilege for reinstalling an LXC template on an existing container. I can't imagine it being that difficult; most of it would be copypasta from other parts of the UI. Behind the scenes it would just delete and recreate, since lxc itself doesn't seem to support "recreating" a container alone.
So before I went ahead, I thought I'd ask if there's any objections to this. I'll have to spend some time finding and reading the relevant code and other research - any pointers in the right direction to anything possibly useful would be appreciated.
I do have one direct question so far. On the dev environment setup doc there are hashes/pound symbols (#'s) before some of the projects listed as required. I am guessing these are either optional or obsolete? If so, do I need any of them for working with PVE5?
As I said I am not a web (or even Linux) developer by profession so I apologize if any of my questions are relatively elementary or tedious to answer. Thanks!
I have an interest in providing linux containers to other users, restricting their access only to what they need to manage their owned container(s). To my surprise I have found one glaring hole in the feature-set - an ability to reinstall the OS for a given container. Looking at the API and user privileges, the closest thing to this is deleting and recreating the container but that can't be restrained to any useful scope e.g. allow a user to only "own" a limited number of CT's (they cannot create more than that number).
I haven't worked on PHP or JS for about a decade and have barely touched the Perl language (I am a Java and C# developer by trade) but I'd be willing to dive in and try to take a crack at adding a button and privilege for reinstalling an LXC template on an existing container. I can't imagine it being that difficult; most of it would be copypasta from other parts of the UI. Behind the scenes it would just delete and recreate, since lxc itself doesn't seem to support "recreating" a container alone.
So before I went ahead, I thought I'd ask if there's any objections to this. I'll have to spend some time finding and reading the relevant code and other research - any pointers in the right direction to anything possibly useful would be appreciated.
I do have one direct question so far. On the dev environment setup doc there are hashes/pound symbols (#'s) before some of the projects listed as required. I am guessing these are either optional or obsolete? If so, do I need any of them for working with PVE5?
As I said I am not a web (or even Linux) developer by profession so I apologize if any of my questions are relatively elementary or tedious to answer. Thanks!
Last edited: