Unable to create new container from template

[avekrivoy]

I made a big mistake by trying to create template of a container with a pct template 107 -experimental 1.
How do I restore it to a running container? The raw image is renamed to base-107-disk-1.raw after this operation.

proxmox-ve: 4.4-88 (running kernel: 4.4.62-1-pve)
pve-manager: 4.4-13 (running version: 4.4-13/7ea56165)
pve-kernel-4.4.10-1-pve: 4.4.10-54
pve-kernel-4.4.62-1-pve: 4.4.62-88
lvm2: 2.02.116-pve3
corosync-pve: 2.4.2-2~pve4+1
libqb0: 1.0.1-1
pve-cluster: 4.0-50
qemu-server: 4.0-110
pve-firmware: 1.1-11
libpve-common-perl: 4.0-95
libpve-access-control: 4.0-23
libpve-storage-perl: 4.0-76
pve-libspice-server1: 0.12.8-2
vncterm: 1.3-2
pve-docs: 4.4-4
pve-qemu-kvm: 2.7.1-4
pve-container: 1.0-100
pve-firewall: 2.0-33
pve-ha-manager: 1.0-40
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u3
lxc-pve: 2.0.7-4
lxcfs: 2.0.6-pve1
criu: 1.6.0-1
novnc-pve: 0.5-9
smartmontools: 6.5+svn4324-1~pve80

 

[avekrivoy]

RESOLVED.
Somehow disk image became readonly and even root couldn't move it or change permission. So I had to copy it to a new image. Then I used this new image as main in my 107.conf. Also, set up Tepmlate: 0
Today I've learned a new wisdom: don't mess with important data in friday at the end of a day.

 

[dcsapak]

just for reference:

when making a container template with 'pct template' you can use it with cloning it ('pct clone'; which is also experimental),

Somehow disk image became readonly and even root couldn't move it or change permission.

we make the base images of a template non-writable, to prevent errors

don't mess with important data in friday at the end of a day.

good old 'read-only friday'