[06:45] <frickler> disable ipv6 by default? are we back in 1998?
[08:59] <shurdeek> hello
[09:00] <shurdeek> I am trying do a PXE+nfs boot of the cloud images. The problem is, the official cloud images don't have the network driver for all the hardware I need. I'm trying to find a way to solve this.
[09:02] <shurdeek> I've spent hours now trying to find out how to build a custom cloud image. Unfortunately I am having problems finding the introductory level documentation. I found out that it probably is done by using live-build. However, I can't find out how to tell live-build to use the cloud-image seed. It always uses the livecd-rootfs seed.
[09:03] <shurdeek> I'd be grateful for documentation on how to do this
[09:07] <shurdeek> or what alternative way of getting the rtl8169 driver into the cloud image
[10:28] <mwhudson> shurdeek: um cloud images are built for vms really
[10:28] <mwhudson> what are you trying to achieve?
[10:55] <RoyK> mwhudson: using cloud images on physical machines, perhaps? ;)
[10:56] <mwhudson> well yes but why
[10:56] <RoyK> no idea whatsoever
[11:05] <shurdeek> mwhudson: I don't necessarily need to use the cloud images on bare metal. I mainly want to use a combination of booting through PXE, mounting rootfs over NFS (or as squashfs image in ram), and cloud-init to customise the system.
[11:06] <shurdeek> I could use something like maas, but that looks like a total overkill for me, and I would have to redesign the network
[11:07] <mwhudson> shurdeek: hmm
[11:07] <shurdeek> if a different image is more suitable then that's ok too
[11:07] <shurdeek> or if there is a scrip to build my own image
[11:08] <mwhudson> hmm, download a squashfs, unpack it, chroot in, install packages, repack it
[11:08] <mwhudson> ?
[11:08] <mwhudson> livecd-rootfs (the thing that makes the images) is a bit difficult to operate, sadly
[11:09] <RoyK> shurdeek: just use a normal image - should work
[11:09] <shurdeek> which image do you recommend for a light server, that supports NFS root and could-init
[11:10] <RoyK> just use the normal server image
[11:10] <RoyK> it's light enough
[11:11] <shurdeek> ok I'll see if it supports what I need
[11:11] <shurdeek> thanks
[11:11] <RoyK> it quite probably will
[11:11] <shurdeek> and how do I build my own one if I want the latest packages?
[11:12] <RoyK> just upgrade later with unattended-upgrades etc
[11:12] <RoyK> or just use ansible to do a full upgrade
[11:13] <RoyK> or whatever floats your ship
[11:13] <shurdeek> ok i'll try
[11:13] <shurdeek> thanks
[12:01] <shurdeek> well, I managed to boot the server image (18.04.5) with nfs root. Unfortunately, it runs the installer rather than a normal startup, and it doesn't seem to execute cloud-init
[12:01] <shurdeek> maybe I'm missing some boot parameters?
[12:05] <RoyK> sorry - never tried this. I've nfs booted things earlier, but not with the installer, just a normal installation and then added some hooks to change things like ssh keys and ip address (if that's set statically). Perhaps this will help? https://ubuntu.com/server/docs/install/autoinstall-quickstart
[12:07] <shurdeek> RoyK: it looks like that could help, there are some argumens there that I haven't tried
[12:20] <RoyK> good luck :)
[12:20] <shurdeek> well, it doesn't seem to work on 18.04 but better on 20.04. The cloud-init executes on 20.04, but it still boots into the installer
[12:59] <bnason> Yea, they apparently released a 1.19.2-00 last night, and trying to force install 1.19.1-00 causes a crash
[13:16] <bnason> And I still can't get it to create the default user for me any more since moving from http to floppy. Here is my current user-data file: https://gist.github.com/bnason/3e268a73adb1d330cb575e7084b19080
[13:17] <bnason> I might just have to switch back to 18.04
[13:19] <ahasenack> bnason: you may get more specific help in the cloud-init channel
[13:19] <ahasenack> oh, sorry, it's about unattended install
[13:20] <ahasenack> there is a forum thread I think about it, have you tried posting there?
[13:20] <ahasenack> the main developer of this is on the other side of the globe
[13:20] <ahasenack> i.e, asleep now
[13:23] <bnason> This one? https://discourse.ubuntu.com/t/please-test-autoinstalls-for-20-04/15250
[13:23] <ahasenack> yeah
[15:10] <bnason> Unfortunately, looks like that topic is kinda dead.
[15:12] <ahasenack> if you post, it will go back to the top
[15:34] <rapidwave> Mysql cannot connect to /var/run/mysqld/mysqld.sock
[15:35] <rapidwave> Says it doesn't exist
[15:37] <compdoc> rapidwave, might want to look thru the many config files in /etc/mysql and see if the location is set somewhere else, or use locate to search for mysqld.sock
[15:38] <rapidwave> locate didn't return any results
[15:38] <compdoc> or read the log files to find why mysql isnt starting
[15:40] <rapidwave> Well...hmm. I try using mysql and it says access denied
[15:41] <rapidwave> I cannot seem to use mysqld_safe because socket doesn't exist
[15:41] <compdoc> does this show anything:  service mysqld status
[15:41] <rapidwave> Could not be found
[15:42] <fridtjof[m]> Isn't it just mysql?
[15:43] <compdoc> how about the command:  dpkg --get-selections | grep mysql
[15:43] <compdoc> shows the same on mine: service mysql status
[15:47] <rapidwave> https://gist.github.com/ojabi/553303c728be56bb460efed2f3a7ce19
[15:50] <compdoc> I think 5.7 is corrent for 18.04
[15:50] <compdoc> correct
[15:52] <rapidwave> I'll remove 8.0 and install 5.7
[15:53] <rapidwave> Wait..I'm using 20.04...
[15:57] <compdoc> how did you install it?
[15:58] <compdoc> my systems are still on 18.04. waiting for them to release the new one for upgrades
[15:58] <teward> 20.04 sounds about right if using 8.0 I think?
[15:59] <rapidwave> I think I'll purge mysql and reinstall
[16:00] <compdoc> let apt install for you
[16:04] <rapidwave> I am
[16:51] <bnason> I'm wondering if the CIDATA floppy still being attached when the VM restarts after the installation is causing this issue. The exact same file works if I use HTTP but not from the floppy. Does anyone know how to disable cloud-init during the autoinstall? `touch /target/etc/cloud/cloud-init.disabled` is what I'm trying right now but no idea if thats enough
[17:09] <bnason> Well I also added "cloud-init=disabled" to the kernel so it's not looking like that is the problems