[06:45] disable ipv6 by default? are we back in 1998? [08:59] hello [09:00] 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] 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] I'd be grateful for documentation on how to do this [09:07] or what alternative way of getting the rtl8169 driver into the cloud image [10:28] shurdeek: um cloud images are built for vms really [10:28] what are you trying to achieve? [10:55] mwhudson: using cloud images on physical machines, perhaps? ;) [10:56] well yes but why [10:56] no idea whatsoever [11:05] 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] 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] shurdeek: hmm [11:07] if a different image is more suitable then that's ok too [11:07] or if there is a scrip to build my own image [11:08] hmm, download a squashfs, unpack it, chroot in, install packages, repack it [11:08] ? [11:08] livecd-rootfs (the thing that makes the images) is a bit difficult to operate, sadly [11:09] shurdeek: just use a normal image - should work [11:09] which image do you recommend for a light server, that supports NFS root and could-init [11:10] just use the normal server image [11:10] it's light enough [11:11] ok I'll see if it supports what I need [11:11] thanks [11:11] it quite probably will [11:11] and how do I build my own one if I want the latest packages? [11:12] just upgrade later with unattended-upgrades etc [11:12] or just use ansible to do a full upgrade [11:13] or whatever floats your ship [11:13] ok i'll try [11:13] thanks [12:01] 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] maybe I'm missing some boot parameters? [12:05] 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] RoyK: it looks like that could help, there are some argumens there that I haven't tried [12:20] good luck :) [12:20] 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] 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] 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] I might just have to switch back to 18.04 [13:19] bnason: you may get more specific help in the cloud-init channel [13:19] oh, sorry, it's about unattended install [13:20] there is a forum thread I think about it, have you tried posting there? [13:20] the main developer of this is on the other side of the globe [13:20] i.e, asleep now [13:23] This one? https://discourse.ubuntu.com/t/please-test-autoinstalls-for-20-04/15250 [13:23] yeah === albech1 is now known as albech === jge is now known as zerosum [15:10] Unfortunately, looks like that topic is kinda dead. [15:12] if you post, it will go back to the top [15:34] Mysql cannot connect to /var/run/mysqld/mysqld.sock [15:35] Says it doesn't exist [15:37] 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] locate didn't return any results [15:38] or read the log files to find why mysql isnt starting [15:40] Well...hmm. I try using mysql and it says access denied [15:41] I cannot seem to use mysqld_safe because socket doesn't exist [15:41] does this show anything: service mysqld status [15:41] Could not be found [15:42] Isn't it just mysql? [15:43] how about the command: dpkg --get-selections | grep mysql [15:43] shows the same on mine: service mysql status [15:47] https://gist.github.com/ojabi/553303c728be56bb460efed2f3a7ce19 [15:50] I think 5.7 is corrent for 18.04 [15:50] correct [15:52] I'll remove 8.0 and install 5.7 [15:53] Wait..I'm using 20.04... [15:57] how did you install it? [15:58] my systems are still on 18.04. waiting for them to release the new one for upgrades [15:58] 20.04 sounds about right if using 8.0 I think? [15:59] I think I'll purge mysql and reinstall [16:00] let apt install for you [16:04] I am === albech1 is now known as albech [16:51] 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] Well I also added "cloud-init=disabled" to the kernel so it's not looking like that is the problems === ijohnson is now known as ijohnson|lunch === ijohnson|lunch is now known as ijohnson