[06:32] <lordievader> Good morning
[16:25] <wrsuser> Is there a way of installing Ubuntu Server (from the new... and far more awful ISO that uses subiquity) without it installing the package 'ubuntu-server' 
[16:25] <wrsuser> Which drags in a whole bunch of things that are frankly really presumptuous to think everyone needs
[16:31] <leftyfb> wrsuser: I'm pretty sure the new server installer just blasts an image onto the drive. If that is the case, you are unlikely to be able to customize what packages are removed 
[16:31] <leftyfb> I could be wrong though
[16:31] <leftyfb> the install goes SUPER quick, leading me to believe it's just an image
[16:31] <wrsuser> yeah I thought that too
[16:31] <wrsuser> People keep asking on IRC and on the forums 'what is it about subiquity you think is missing!? oh but it's so lovely, tell us!' ... well that really... without the 'ubuntu-server' package... it at least has a better hope in hell of being closer to what mini.iso did
[16:31] <rbasak> I think that's right. You can install it manually by doing what the installer would do. All sources are available, etc, so ultimately any customisation you want is possible. But you need to know what you're doing to avoid leaving yourself latent issues.
[16:32] <wrsuser> subiquity is hell
[16:33] <leftyfb> for customization, sure. If that's what you want, then use the other installer and/or debootstrap
[16:33] <wrsuser> there is no supported/official other installer any more
[16:34] <leftyfb> wrsuser: http://archive.ubuntu.com/ubuntu/dists/focal/main/installer-amd64/current/legacy-images/netboot/mini.iso
[16:35] <rbasak> It was never supported in the first place: https://discourse.ubuntu.com/t/netbooting-the-live-server-installer/14510/10?u=rbasak
[16:35] <wrsuser> You did see I already mentioned 'mini.iso' right?
[16:36] <leftyfb> wrsuser: mini.iso doesn't use subiquity 
[16:36] <wrsuser> I already know that!
[16:37] <leftyfb> wrsuser: ok, so what's wrong with using that?
[16:37] <wrsuser> It's a) not "supported", b) out of date, c) won't exist in the next LTS at all, d) doesn't even give you a proper login prompt on reboot
[16:37] <wrsuser> basically... abandoned long ago
[16:38] <wrsuser> I'm NOT using subiquity out of choice :P
[16:42] <leftyfb> wrsuser: you could use cloud-init to customize the install on first boot
[16:42] <leftyfb> wrsuser: other than that, I don't think there's a supported solution 
[16:54] <JanC> maybe the subiquity installer can be improved to allow choosing between multiple images...?
[16:54] <catalase> can someone advise on how to get this line: /home/ubuntu/update.sh | while IFS= read -r line; do printf '%s %s\n' "$(date)" "$line"; done >> /home/ubuntu/update.log; to work in sudo crontab -e
[16:55] <sarnold> catalase: best to create that as a shell script and just call the script. that's complicated enough that doing it in a cron one-liner is probably annoying
[17:28] <wrsuser> JanC, isn't the ISO large enough? :D  it's like 1.2gb!!
[17:28] <wrsuser> for a SERVER install lol
[17:30] <JanC> it's not like a minimal image would add much to that
[18:03] <wrsuser> on a fresh ubuntu server 20.04 install... why (on first and subsequent bootups) do I get the usual... 
[18:03] <wrsuser> [  OK  ] Started Network Name Resolution.
[18:03] <wrsuser> [  OK  ] Reached target Host and Network Name Lookups.
[18:03] <wrsuser> ... but then it'll wait for a full 2 minutes doing naff all on... 
[18:03] <wrsuser> [   ***] A start job is running for Wait for Network to be Configured (1min 5s / no limit)
[18:03] <wrsuser> is this some cloud-init bullshit without it telling me?
[18:04] <jrwren> not likely. more likely is some systemd service not starting correctly.
[18:06] <wrsuser> i think it might be something to do with it being a NUC
[18:07] <wrsuser> like subiquity has thought it'd be a bright idea to configure things by default to try dhcp on BOTH wired and wireless interfaces
[18:09] <wrsuser> or actually maybe even trying dhcp on all 3 wired interfaces
[18:14] <Odd_Bloke> IIRC, Wait for Network to be Configured blocks until it has networking on _an_ interface that's configured, not every interface that's configured.
[18:17] <wrsuser> https://i.snipboard.io/NqAHYw.jpg
[18:17] <wrsuser> i took photos of each silly subiquity step 
[18:17] <wrsuser> i left this screen as it was and just moved on
[18:18] <wrsuser> but my guess is because it's set to 'DHCPv4' on all 3 wired ethernet interfaces (even though the other two are USB ethernet devices) ... the install on disk tries DHCPv4 on all 3 interfaces too
[18:19] <wrsuser> i don't remember there being an option at install time to tell it *not* to use those interfaces
[18:45] <Odd_Bloke> So does eno1 in this case have networking?
[19:10] <wrsuser> Odd_Bloke, yeah
[19:10] <wrsuser> but the other two enx* interfaces didn't have anything plugged into them
[19:13] <wrsuser> where the heck does a fresh ubuntu server install even keep it's network config?  because it's not in /etc/network/interfaces and it's not in /etc/NetworkManager either by looks of it
[19:14] <wrsuser> but I'm betting wherever it is... the installer set the two unused interfaces to dhcp 
[19:14] <wrsuser> 'netplan' what the heck is that
[19:15] <wrsuser> and yup 00-installer-config.yaml has them set to dhcp
[19:15] <tomreyn> what did you do those past 5 years when you weren't using computers?
[19:15] <wrsuser> oh so I really hate subiquity and the silly notion of a 'ubuntu-server' spin 
[19:15] <jrwren> ubuntu has changed!
[19:15] <wrsuser> tomreyn, for servers?  I used Debian :P
[19:16] <tomreyn> oh, well, ubuntu isn't debian. and less so with each new release.
[19:16] <wrsuser> desktop ubuntu isn't using netplan though right? 
[19:17] <tomreyn> desktop uses network manager without netplan. you could make desktop use netplan, too, if oyu wanted, as oyu can make server use network manager with or without netplan, too
[19:17] <wrsuser> ah :)  just a file that says use networkmanager :P
[19:17] <tomreyn> but server defaults to systemd-networkd with netplan
[19:17] <wrsuser> yeah I'm really hating this - that's yet another thing to fix then
[19:18] <tomreyn> current systemd-networkd config will be in /run/
[19:18] <wrsuser> my goal here is to build a desktop (technically a terminal server, but essentially that's 99% a desktop) and have it as close to desktop defaults as possible
[19:18] <wrsuser> so network-manager instead of "netplan" for example
[19:18] <wrsuser> this server ISO is just horrid for this task
[19:19] <jrwren> can you apt install ubuntu-desktop and get something closer to what you want?
[19:20] <wrsuser> that's not going to undo all the stuff that subiquity preconfigured for a server approach (e.g. like netplan... and installing the 'ubuntu-server' metapackage)
[19:20] <wrsuser> and who knows how many other things...
[19:20] <wrsuser> it's just not a proper substitute for mini.iso (which after I briefly tried it... reminds me a lot of the debian netinst ISO... i.e. both the installer and the subset of packages that got installed) 
[19:22] <tomreyn> there's debootstrap
[19:22] <wrsuser> that's not really comparable
[19:23] <tomreyn> to debian-installer? no, but it provides the most flexibility
[19:24] <TJ-> debootstrap or mkosi for total customisation functionality. mkosi is better for customisations
[19:24] <wrsuser> with a debian-netinst/ubuntu-mini.iso...-like approach... you didn't have to worry about installing extra packages that the system may need (e.g. intel microcode, open-vm-tools, etc...)... or partitioning... or installing a bootloader... or setting up a host file... or a million other things.
[19:24] <TJ-> mkosi can produce bootable raw disk images, or simple root-file-systems
[19:24] <wrsuser> you could just fill in that debian-installer wizard with a wrist most times (I've done it that often) and bingo... a working system you can get straight to apt-get'ing whatever extra you need
[19:25] <wrsuser> debootstrap is NOT comparable and no substitute 
[19:25] <wrsuser> the extra hassle only makes sense if you doing a MASSIVE amount of systems regularly
[19:26] <TJ-> sounds like all the time you've spent on this, deboostrap/mkosi could have done 90% of the work in 2 minutes
[19:41] <teward> cpaelzer: fyi I am not an expert in the Lua module on NGINX, but check to make sure the lua jit stuff is in build-depends and that it actually installs and doesn't fail
[19:41] <teward> that's the only reason your build failure as indicated would happen to my knowledge if it's not provided and not in ld
[19:42] <teward> that's the only reason your build failure as indicated would happen to my knowledge if it's not provided and not in ldd or w/eit is (brain isn't working >.>)