Promox 6.0-9: can't create container with Ubuntu 19.10-1

[Zamana]

Hi!

I just tried to create a container using the Ubuntu-19.10-1 template and got this error:

extracting archive '/var/lib/vz/template/cache/ubuntu-19.10-standard_19.10-1_amd64.tar.gz'
Total bytes read: 675983360 (645MiB, 90MiB/s)
Detected container architecture: amd64
TASK ERROR: unable to create CT 114 - unsupported Ubuntu version '19.10'

Does anybody knows what's going on?

 

[LnxBil]

Does anybody knows what's going on?

Yes, I do.


Oh, you want more?

Every Ubuntu version has to be explicitly be included in the LXC guest OS detection and your version does not include that. I haven't tracked the git commits over this week, but I already fixed it in a test I did last weekend. You can wait for the official patch (best) or if you want it now, you can fix it yourself in file /usr/share/perl5/PVE/LXC/Setup/Ubuntu.pm.

 

[t.lamprecht]

Hi!

I just tried to create a container using the Ubuntu-19.10-1 template and got this error:

extracting archive '/var/lib/vz/template/cache/ubuntu-19.10-standard_19.10-1_amd64.tar.gz'
Total bytes read: 675983360 (645MiB, 90MiB/s)
Detected container architecture: amd64
TASK ERROR: unable to create CT 114 - unsupported Ubuntu version '19.10'

Does anybody knows what's going on?

If you update pve-container to 3.0-9 or newer it will work. This update is not yet avaiolable on the enterprise repository, though. (will be soon)

 

[Zamana]

Hi!

Thanks for the explanations.

I just thought that as I was able to download this specific template version it was already supported/included/whatever in Proxmox.

Thanks.
Regards.

 

[t.lamprecht]

I just thought that as I was able to download this specific template version it was already supported/included/whatever in Proxmox.

Yeah, it's slightly confusing I know. To have the full explanation and rationale for this specific situation:
This time I only got around testing the new release once it was almost done, so template upload and initial release of a compatible pve-container was done at the same time.. The container Debian package needs to go down our testing/repo cascade (internal -> pvetest -> no-subscription -> enterprise) but the ct template itself has only (internal -> public).. I though about delaying the template upload, but as people can update existing ones anyway I did not see value in that (and did not want to forget it).. This time quite big feature update (pending changes for CTs) was coupled with the "allow Ubuntu 19.10" update, so we moved it a bit more carefully from down the repo cascade, to ensure the least possible breakage of this bigger change gets released.

But you did good in asking, sometimes, with all the avialble templates, a release of a new version may get overseen, so reminders from the community are appreciated.

 

[SysAdman]

I'm having this same issue with

xtracting archive '/var/lib/vz/template/cache/ubuntu-20.10-standard_20.10-1_amd64.tar.gz'
tar: Skipping to next header
Total bytes read: 37509120 (36MiB, 100MiB/s)
tar: Exiting with failure status due to previous errors
TASK ERROR: unable to create CT 100 - 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/100/rootfs --skip-old-files --anchored --exclude './dev/*'' failed: exit code 2

Going to try an older template and report back.

UPDATE:
It works for Ubuntu 20.04-

extracting archive '/var/lib/vz/template/cache/ubuntu-20.04-standard_20.04-1_amd64.tar.gz'
Total bytes read: 669050880 (639MiB, 108MiB/s)
Detected container architecture: amd64
Creating SSH host key 'ssh_host_rsa_key' - this may take some time ...
done: SHA256:bPjBkAybalHmoqoPUKmjFslzIKoLRF/pnUt+QJywg6M root@matterhorn
Creating SSH host key 'ssh_host_ecdsa_key' - this may take some time ...
done: SHA256s0PNVlIse0WfQAQWVJ4/bPdsrUusXTZmpAhqvDOKm4 root@matterhorn
Creating SSH host key 'ssh_host_dsa_key' - this may take some time ...
done: SHA256:4H0+lp1a8xDiMdcQ3RgJurtpza/eAtTveFSYiQ4WKb4 root@matterhorn
Creating SSH host key 'ssh_host_ed25519_key' - this may take some time ...
done: SHA256:1WwE7EeUB0iErnWf8rfKIp0jei0TYmgnskPzNvFWhfo root@matterhorn
TASK OK

 

[fiona]

Hi,
please don't bump such old threads, but create a new one next time. It's unlikely to be the same issue, because the error message is different.

I'm having this same issue with

xtracting archive '/var/lib/vz/template/cache/ubuntu-20.10-standard_20.10-1_amd64.tar.gz'
tar: Skipping to next header
Total bytes read: 37509120 (36MiB, 100MiB/s)
tar: Exiting with failure status due to previous errors
TASK ERROR: unable to create CT 100 - 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/100/rootfs --skip-old-files --anchored --exclude './dev/*'' failed: exit code 2

This looks like the tar file in question is corrupted, could you try re-downloading the template and see if it still fails?

 

[SysAdman]

Apologies Fabian, will create a new thread next time. That was already the third or fourth attempt at downloading the archive so I gave up and went to prior version. I'll stick with 20.04 just now as it's working for me. Thanks for the reply though.

Regards.

 

[fiona]

What is the checksum of the file? For me it's

# sha512sum ubuntu-20.10-standard_20.10-1_amd64.tar.gz
30fe89a4c5b5afa470240016fc588a4ea12de20d94804c8bd3999d618ef0f78348a9a6d383a7140b8677d6041d05d4f56f35c0e17cf9141139b200183ec69664  ubuntu-20.10-standard_20.10-1_amd64.tar.gz

Maybe also try updating the database with pveam update (might take a while) before downloading.

 

[SysAdman]

SOLVED!!

Was having problems with backups and deploying the originally working 20.04 template to a second container, so I figured I’d have to do some Proxmox GRUB memtests.

Turns out 2 of my sticks were faulty, they are about 10 years old, I toasted them in 20mins during the memtests such that the system wouldn’t even POST while either one was inserted in the motherboard.

Running on the remaining 2 healthy sticks and all my archiving issues have disappeared. I’ve just ordered a couple of replacements off ebay

Thanks again for the suggestions and sorry for bumping old thread but hopefully anyone else experiencing this will think to run memtest86 from the Proxmox GRUB boot loader menu.