TASK ERROR: you can't start a CT if it's a template

max2france

Renowned Member
Feb 10, 2016
15
0
66
45
Hi,

I create a lxc contenair that work well, I wanted to create a model, so I click "convert to template".

Now my lxc does not want to start because it is considered one template.

And this template, I do not know use it to create a new contenair LXC.

At start, I have this error message:

TASK ERROR: you can't start a CT if it's a template

Are you it has a way to find my LX as before?

Thank you in advance for your help,

Max
 
are you running an uptodate version? please post the output of "pveversion -v"

the convert to template option for LXC containers was removed from the web interface a while ago because it was included early by accident. you should be able to create an instance of your template on the command line with "pct clone" (check "man pct" for details). the GUI options will be re-introduced in the near future.
 
root@srv23:~# pveversion -v
proxmox-ve: 4.1-39 (running kernel: 4.2.8-1-pve)
pve-manager: 4.1-15 (running version: 4.1-15/8cd55b52)
pve-kernel-4.2.6-1-pve: 4.2.6-36
pve-kernel-4.2.8-1-pve: 4.2.8-39
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 1.0-1
pve-cluster: 4.0-33
qemu-server: 4.0-62
pve-firmware: 1.1-7
libpve-common-perl: 4.0-49
libpve-access-control: 4.0-11
libpve-storage-perl: 4.0-42
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.5-8
pve-container: 1.0-46
pve-firewall: 2.0-18
pve-ha-manager: 1.0-23
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.5-7
lxcfs: 2.0.0-pve1
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve7~jessie
 
I have my id lxc 102 to 110 with the command:

root@srv23:~# pct clone 102 110
create linked clone of mountpoint rootfs (local:102/base-102-disk-1.raw)
clone 102/base-102-disk-1.raw: images, vm-110-disk-1.qcow2, 110 to vm-110-disk-1.qcow2 (base=../102/base-102-disk-1.raw)
Formatting '/var/lib/vz/images/110/vm-110-disk-1.qcow2', fmt=qcow2 size=21474836480 backing_file=../102/base-102-disk-1.raw encryption=off cluster_size=65536 lazy_refcounts=off refcount_bits=16


but I have this message to boot :

lxc-start: lxc_start.c: main: 344 The container failed to start.
lxc-start: lxc_start.c: main: 346 To get more details, run the container in foreground mode.
lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options.
TASK ERROR: command 'lxc-start -n 110' failed: exit code 1
 
please update your installation to the current version.

to get a more detailled output, you can run "lxc-start -n 110 -F -lDEBUG -o /tmp/lxc.log", the resulting log file is in /tmp/lxc.log . note that lxc-start does not terminate if the container boots, you will have to shut it down from another shell (with "pct shutdown" or by logging in and shutting it down from within the container).
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!