Re: [pve-devel] [PATCH container 1/1] add hookscript to containers

2019-01-23 Thread Fabian Grünbichler
On Wed, Jan 23, 2019 at 03:38:21PM +0100, Dominik Csapak wrote: > On 1/23/19 3:29 PM, Fabian Grünbichler wrote: > > same as qemu-server, I'd limit adding a hookscript to a CT config to > > root@pam (for now). > > yes you are correct > > i thought we had the same default as for vms (new ones defau

Re: [pve-devel] [PATCH container 1/1] add hookscript to containers

2019-01-23 Thread Dominik Csapak
On 1/23/19 3:29 PM, Fabian Grünbichler wrote: same as qemu-server, I'd limit adding a hookscript to a CT config to root@pam (for now). yes you are correct i thought we had the same default as for vms (new ones default to root@pam only, maybe we should do this for cts also?) On Mon, Jan 21,

Re: [pve-devel] [PATCH container 1/1] add hookscript to containers

2019-01-23 Thread Fabian Grünbichler
same as qemu-server, I'd limit adding a hookscript to a CT config to root@pam (for now). On Mon, Jan 21, 2019 at 09:44:36AM +0100, Dominik Csapak wrote: > this adds the config (hookscript) and executes it > on four points in time for the container > > the same notes as with vms are in place regar

[pve-devel] [PATCH container 1/1] add hookscript to containers

2019-01-21 Thread Dominik Csapak
this adds the config (hookscript) and executes it on four points in time for the container the same notes as with vms are in place regarding when the script is called Signed-off-by: Dominik Csapak --- src/PVE/LXC.pm| 6 ++ src/PVE/LXC/Config.pm | 18 +- src/