hi proxmox infomation is:
created a basic ubuntu server ct , from template, converted to template:
when execute link clone with gui got error:
and
ct fullclone , kvm fullclone, kvm linkclone with there's converted template is all fine.
can proxmox team fix that?
thanks anyway
Code:
proxmox-ve: 7.0-2 (running kernel: 5.11.22-4-pve)
pve-manager: 7.0-11 (running version: 7.0-11/63d82f4e)
pve-kernel-5.11: 7.0-7
pve-kernel-helper: 7.0-7
pve-kernel-5.11.22-4-pve: 5.11.22-9
pve-kernel-5.11.22-3-pve: 5.11.22-7
ceph-fuse: 16.2.6-pve2
corosync: 3.1.5-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: residual config
ifupdown2: 3.1.0-1+pmx3
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve1
libproxmox-acme-perl: 1.3.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.0-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-9
libpve-guest-common-perl: 4.0-2
libpve-http-server-perl: 4.0-2
libpve-storage-perl: 7.0-11
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-4
lxcfs: 4.0.8-pve2
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.0.10-1
proxmox-backup-file-restore: 2.0.10-1
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.3-6
pve-cluster: 7.0-3
pve-container: 4.0-9
pve-docs: 7.0-5
pve-edk2-firmware: 3.20200531-1
pve-firewall: 4.2-3
pve-firmware: 3.3-1
pve-ha-manager: 3.3-1
pve-i18n: 2.5-1
pve-qemu-kvm: 6.0.0-4
pve-xtermjs: 4.12.0-1
qemu-server: 7.0-14
smartmontools: 7.2-pve2
spiceterm: 3.2-2
vncterm: 1.7-1
zfsutils-linux: 2.0.5-pve1
created a basic ubuntu server ct , from template, converted to template:
Code:
cat /etc/pve/nodes/pve/lxc/1002.conf
arch: amd64
cores: 1
features: nesting=1
hostname: CT1001
memory: 1024
net0: name=eth0,bridge=vmbr1,hwaddr=86:0C:5E:73:F5:1A,ip=dhcp,type=veth
ostype: ubuntu
rootfs: local:1002/base-1002-disk-0.raw,size=10G
swap: 0
template: 1
unprivileged: 1
when execute link clone with gui got error:
Code:
Linked clone feature for 'local:1002/base-1002-disk-0.raw' is not available (500)
and
ct fullclone , kvm fullclone, kvm linkclone with there's converted template is all fine.
can proxmox team fix that?
thanks anyway
Last edited: