Search results

Any update on this? Is this issue resolved in later releases?

I believe this may be inching close to the core issue. VM 117 was an LXC container that was converted to a template through the Proxmox GUI. This causes the disk image to be renamed (or cloned, perhaps?) The container template lists the following rootfs in its configuration: root@p:~# pvesh...

We are having the same issue when trying to delete container templates: On first attempt to delete (after all linked clones are removed): 2019-01-10 15:48:27.548015 7f56b1375100 -1 did not load config file, using default settings. 2019-01-10 15:48:27.653172 7f770032c100 -1 did not load config...