Search results

I want simple and maintainable deployment of containers. Some containers will need different system packages installed after first boot, for example. Not all containers will have the same deployment environment though. I realize now that hook scripts are probably not the way to go for this.

I did not realize that hook scripts were run on the PVE host as it wasn't mentioned anywhere in the documentation that I saw. If I wanted to execute a command within a container from a hook script, then I would also have to use pct exec in the hook script since the hook script itself is running...

What is the order of execution for when an LXC container is started when it has both a mount point (bind mount in this case) and a hook script set? Example lxc config: hostname: ct1 ostype: debian arch: amd64 cores: 1 memory: 1024 swap: 1024 rootfs: local:100/vm-100-disk-0.raw,size=10G onboot...

Yes, the "protection" config flag is what I want. I was going down the wrong path after seeing the "lock" config. Perhaps it should say in the man page that pct set <vmid> --lock is meant for internal use only and should not be used by the end user. If it had said that it would have saved me a...

I was hoping to use the locks to help prevent accidental deletion of a vm/ct. After doing some testing, it would appear that if the vm has any lock on it at all, you just can't change any config settings on it or even start/stop it. For example if I add a "backup" lock on a ct, I cannot destroy...

Can somebody please explain the details about the pct set <vmid> --lock and the pct unlock commands? The man pages say nothing about this config setting other than "Lock/unlock the VM.". There is a list of possible lock types (backup, create, destroyed, disk, fstrim, migrate, mounted, rollback...