Replace di-live with default Debian installer and leverage default Debian Live support

[JedMeister]

Beyond the specific issue/feature noted in the subject, this is a meta-issue covering other install related bugs/issues.

Once the relevant Debian components (debian installer, debian live, etc) are integrated into TurnKey and this issue is closed, it should (or at least hopefully) also address the following issues:

• support for di-live preseeding #149
• Full filesystem encryption option on install #166
• Di-live support for UEFI install #1435
• [ISO install] on VMware products fails to autodetect where to install grub #1456
• di-live - LVM - install loop if you change your mind #1490

Preliminary work has already been done by @a3s7p - see https://github.com/a3s7p/tklive & internal testing is in progress. Once complete, "rc" builds of Core and Lamp will be published (perhaps others?). The anticipated ISO naming for v18.x based builds will include uefi in the name to differentiate from the current v18.x builds. E.g.

turnkey-core-uefi-18.0rc1-bookworm-amd64.iso

(or similar).

Assuming all goes well, these builds will be the default (probably only) builds for v19.x+

[OnGle]

Images built by tklive seem to not run correctly either in virtualized UEFI or BIOS with proxmox, it boots in both, so that's a promising start, but both fail to complete the install process (fail at "installing system")

(proxmox qemu/kvm environment is QEMU emulator version 9.0.2 (pve-qemu-kvm_9.0.2-2))

I checked if the normal debian iso works on both just out of interest and had no issues. Not really sure what could be the issue here.

[JedMeister]

That sucks, but thanks for testing @OnGle. We'll need to relook at this although it's not priority (yet). I'll leave the PR unmerged and this issue open...

[a3s7p]

Thanks @OnGle, could you get detailed logs from the installer?

There's an option in the "main" menu to dump logs.

[JedMeister]

Thanks @OnGle, could you get detailed logs from the installer?

There's an option in the "main" menu to dump logs.

Beyond that, I just had a quick poke around the debian docs and have some additional thoughts - apparently you should be able to access VT1 and/or VT4 and from there dmesg might have some info too? The manual also suggests checking in /var/log to see if there is anything there. The manual explictly notes /var/log/syslog although IIRC we don't install that anymore (just rely on the systemd journal). Perhaps I'm wrong, but I suspect that there isn't any journaling early in the install. If that's the case, then adding syslog-ng - or rsyslog - to the ISO might be worth a try IMO.

There is also a installation-report package. AFAICT that's specifically intended to generate a report which can be attached to a new Debian bug. However pre-installing that give some additional info?

[OnGle]

Alright I've collected the logs + dmesg for both bios and uefi install attempts.
I had a quick look at installation-report, but it only includes hw info, which is already included in the debug logs.

This was tested from an up-to-date core-iso that has been hybridized using instructions from tklive. Let me know if you need any more info from my end.

bios_install.tar.gz
uefi_install.tar.gz

[a3s7p]

Thanks @OnGle, looks like this is the culprit:

Feb 19 03:58:14 base-installer: error: The tar process copying the live system failed (only 39019 out of 39043 files have been copied, last file was ).
Feb 19 03:58:14 main-menu[828]: (process:6216): tar: ./var/spool/postfix/private/anvil: socket ignored
Feb 19 03:58:14 main-menu[828]: (process:6216): tar: ./var/spool/postfix/private/bounce: socket ignored
Feb 19 03:58:14 main-menu[828]: (process:6216): tar: ./var/spool/postfix/private/bsmtp: socket ignored
Feb 19 03:58:14 main-menu[828]: (process:6216): tar: ./var/spool/postfix/private/defer: socket ignored
Feb 19 03:58:14 main-menu[828]: (process:6216): tar: ./var/spool/postfix/private/discard: socket ignored
Feb 19 03:58:14 main-menu[828]: (process:6216): tar: ./var/spool/postfix/private/error: socket ignored
Feb 19 03:58:14 main-menu[828]: (process:6216): tar: ./var/spool/postfix/private/ifmail: socket ignored
Feb 19 03:58:14 main-menu[828]: (process:6216): tar: ./var/spool/postfix/private/lmtp: socket ignored
Feb 19 03:58:14 main-menu[828]: (process:6216): tar: ./var/spool/postfix/private/local: socket ignored
Feb 19 03:58:14 main-menu[828]: (process:6216): tar: ./var/spool/postfix/private/maildrop: socket ignored
Feb 19 03:58:14 main-menu[828]: (process:6216): tar: ./var/spool/postfix/private/mailman: socket ignored
Feb 19 03:58:14 main-menu[828]: (process:6216): tar: ./var/spool/postfix/private/proxymap: socket ignored
Feb 19 03:58:14 main-menu[828]: (process:6216): tar: ./var/spool/postfix/private/proxywrite: socket ignored
Feb 19 03:58:14 main-menu[828]: (process:6216): tar: ./var/spool/postfix/private/relay: socket ignored
Feb 19 03:58:14 main-menu[828]: (process:6216): tar: ./var/spool/postfix/private/retry: socket ignored
Feb 19 03:58:14 main-menu[828]: (process:6216): tar: ./var/spool/postfix/private/rewrite: socket ignored
Feb 19 03:58:14 main-menu[828]: (process:6216): tar: ./var/spool/postfix/private/scache: socket ignored
Feb 19 03:58:14 main-menu[828]: (process:6216): tar: ./var/spool/postfix/private/scalemail-backend: socket ignored
Feb 19 03:58:14 main-menu[828]: (process:6216): tar: ./var/spool/postfix/private/smtp: socket ignored
Feb 19 03:58:14 main-menu[828]: (process:6216): tar: ./var/spool/postfix/private/tlsmgr: socket ignored
Feb 19 03:58:14 main-menu[828]: (process:6216): tar: ./var/spool/postfix/private/trace: socket ignored
Feb 19 03:58:14 main-menu[828]: (process:6216): tar: ./var/spool/postfix/private/uucp: socket ignored
Feb 19 03:58:14 main-menu[828]: (process:6216): tar: ./var/spool/postfix/private/verify: socket ignored
Feb 19 03:58:14 main-menu[828]: (process:6216): tar: ./var/spool/postfix/private/virtual: socket ignored
Feb 19 03:58:14 main-menu[828]: (process:6216): tar: ./var/spool/postfix/public/cleanup: socket ignored
Feb 19 03:58:14 main-menu[828]: (process:6216): tar: ./var/spool/postfix/public/flush: socket ignored
Feb 19 03:58:14 main-menu[828]: (process:6216): tar: ./var/spool/postfix/public/pickup: socket ignored
Feb 19 03:58:14 main-menu[828]: (process:6216): tar: ./var/spool/postfix/public/postlog: socket ignored
Feb 19 03:58:14 main-menu[828]: (process:6216): tar: ./var/spool/postfix/public/qmgr: socket ignored
Feb 19 03:58:14 main-menu[828]: (process:6216): tar: ./var/spool/postfix/public/showq: socket ignored
Feb 19 03:58:14 main-menu[828]: WARNING **: Configuring 'live-installer' failed with error code 1

I ran into this a few times over the years. Maybe here as well but I don't remember what I did to fix it now. Basically tar returns 1 for this entirely non-serious error condition.

We'll need to avoid feeding it sockets. Maybe skip setting up / running postfix on the live system as the utility of that is questionable anyhow. I will handle that.