Turnkey Templates Always Fail to Install

T

theoisadoor

New Member
Feb 3, 2025
4
0
1
I am trying to install the Turnkey templates, however whenever I start the installation, it always fails with a completely useless error:
Code: 
Logical volume "vm-20200-disk-0" created.
Creating filesystem with 16777216 4k blocks and 4194304 inodes
Filesystem UUID: 5e7227c2-c26b-4848-8094-2a6b6fd7f6fd
Superblock backups stored on blocks:
    32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
    4096000, 7962624, 11239424
extracting archive '/mnt/pve/HL1-TRUENAS01.50/template/cache/debian-12-turnkey-gitea_18.0-1_amd64.tar.gz'
tar: Skipping to next header
Total bytes read: 284395520 (272MiB, 133MiB/s)
tar: Exiting with failure status due to previous errors
  Logical volume "vm-20200-disk-0" successfully removed.
TASK ERROR: unable to create CT 20200 - command 'tar xpf - -z --totals --one-file-system -p --sparse --numeric-owner --acls --xattrs '--xattrs-include=user.*' '--xattrs-include=security.capability' '--warning=no-file-ignored' '--warning=no-xattr-write' -C /var/lib/lxc/20200/rootfs --skip-old-files --anchored --exclude './dev/*'' failed: exit code 2
"Exiting with failure status due to previous errors" does not help whatsoever as there are no previous errors in the output. This happens when installing as either privileged and unprivileged. I can install the debian-12-standard_12.7-1_amd64.tar.zst template no problem so its not like container installation is failing altogether, I am only getting this with Turnkey templates. The above error was for the debian-12-turnkey-gitea_18.0-1_amd64.tar.gz image. Can anyone assist?
 
fba said:
Did you verify the downloaded file by using a checksum? This can be done during import also.

sounds like a damaged file
Click to expand...
Hi, yep, they were all downloaded directly via CT Templates > Templates with the following output:
Code: 
downloading http://mirror.turnkeylinux.org/turnkeylinux/images/proxmox/debian-12-turnkey-gitea_18.0-1_amd64.tar.gz to /mnt/pve/HL1-TRUENAS01.50/template/cache/debian-12-turnkey-gitea_18.0-1_amd64.tar.gz
--2025-02-03 15:49:41--  http://mirror.turnkeylinux.org/turnkeylinux/images/proxmox/debian-12-turnkey-gitea_18.0-1_amd64.tar.gz
Resolving mirror.turnkeylinux.org (mirror.turnkeylinux.org)... 137.226.34.46, 131.188.12.211, 2801:82:80ff:8000::e
Connecting to mirror.turnkeylinux.org (mirror.turnkeylinux.org)|137.226.34.46|:80... failed: Connection timed out.
Connecting to mirror.turnkeylinux.org (mirror.turnkeylinux.org)|131.188.12.211|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 342769024 (327M) [application/x-gzip]
Saving to: '/mnt/pve/HL1-TRUENAS01.50/template/cache/debian-12-turnkey-gitea_18.0-1_amd64.tar.gz.tmp_dwnl.4177780'
     0K ........ ........ ........ ........  9% 1.74M 2m49s
 32768K ........ ........ ........ ........ 19% 4.42M 1m45s
 65536K ........ ........ ........ ........ 29% 3.92M 81s
 98304K ........ ........ ........ ........ 39% 4.12M 65s
131072K ........ ........ ........ ........ 48% 1.88M 61s
163840K ........ ........ ........ ........ 58% 1.28M 59s
196608K ........ ........ ........ ........ 68% 2.00M 46s
229376K ........ ........ ........ ........ 78% 1.72M 33s
262144K ........ ........ ........ ........ 88% 1.15M 20s
294912K ........ ........ ........ ........ 97% 1.21M 4s
327680K ......                             100% 1002K=2m59s
2025-02-03 15:54:57 (1.82 MB/s) - '/mnt/pve/HL1-TRUENAS01.50/template/cache/debian-12-turnkey-gitea_18.0-1_amd64.tar.gz.tmp_dwnl.4177780' saved [342769024/342769024]
calculating checksum...OK, checksum verified
download of 'http://mirror.turnkeylinux.org/turnkeylinux/images/proxmox/debian-12-turnkey-gitea_18.0-1_amd64.tar.gz' to '/mnt/pve/HL1-TRUENAS01.50/template/cache/debian-12-turnkey-gitea_18.0-1_amd64.tar.gz' finished
TASK OK
So whatever checksum comes as default is validating as can be seen above. If it's/they're all corrupt, then that means all of the Turnkey templates are dodgy (highly doubt) or there is no actual checksum validation being performed.
 
Just calculated the checksum and got the following:
Bash: 
$ sha256sum /mnt/pve/HL1-TRUENAS01.50/template/cache/debian-12-turnkey-gitea_18.0-1_amd64.tar.gz
dc4e79adf2c2479c042fd2c661821ce5da31d2ad6e72502a4a3f3c5dcdce0246  /mnt/pve/HL1-TRUENAS01.50/template/cache/debian-12-turnkey-gitea_18.0-1_amd64.tar.gz
When I check the official Turnkey hashes they do not match:
Code: 
$ sha256sum debian-12-turnkey-gitea_18.0-1_amd64.tar.gz
42fd8471cb4bbb2fa5e94dcef94805b32d9400b28dd7f067a994511199f901ed  debian-12-turnkey-gitea_18.0-1_amd64.tar.gz
I guess this calls into question what checksum validation PVE does against the templates?
 
Just downloaded twice more, each time I download from CT Templates > Templates I get a different sha256sum. There is something inherently wrong with the checksum validation in place, or at least it should not be declaring that a checksum has been verified.
 
I downloaded this file on my PVE and used the built-in validation by providing the sha256 checksum from Turnkey's download page. It worked out as expected and I could start a container with it. So my assumption is, that the file provided by Turnkey is working as expected.
calculating checksum...OK, checksum verified
Click to expand...
Getting this output without having a checksum provided is indeed irritating.
 
You must log in or register to reply here.
Top Bottom