[09:43] <Lope>  On a fresh install of Ubuntu 22.04.4 LTS. I'm running 9 LXC containers, all the same web server development purposes, but obviously different LXC configs for each one, with a unique MAC and so on. I can't start the 10th container. Unless I stop the Nth container, then I can start the 10th container. I've got plenty of free RAM. root's ulimit was 1024, I increased it to 4096, didn't help. Any ideas?
[09:43] <Lope> There's no error, return value is zero. dmesg and syslog don't say anything. I try start the container in foreground or background, makes no diff.
[09:53] <Lope> I dunno WTF. It started working.
[09:53] <Lope> I just started the container in debug mode. It started fine. Stopped it. Started it in background mode and it's working.
[14:10] <fastidious> For those of you writing technical documentation, how do you style an application name? For example, if talking about sed, do you use `sed`, or "sed", or *sed*, or **sed**?
[14:17] <miceiken> So I've been running a node promotheus exporter to try to identify my network issue (IRC timing out in the night hours) and I see that for about a minute when I disconnected the eno1 physical link state went from 1 to 0 for about a minute. So I'm assuming the physical link went down. Is there any way for me to get more information about this?
[14:21] <miceiken> https://paste.mozilla.org/kdBeyo3d <- from systemd-networkd
[14:26] <miceiken> actually, https://paste.mozilla.org/Fi2PcCCB happens to both wifi and ethernet
[14:27] <CosmicDJ> fastidious: there are plenty of style guides out there, pick the one you like https://developers.google.com/style https://redhat-documentation.github.io/supplementary-style-guide/ https://learn.microsoft.com/en-us/style-guide/welcome/ https://help.apple.com/applestyleguide/
[14:40] <fastidious> CosmicDJ: Those are helpful, thanks. My question was broader, and personal, but if I am to assume anyone is using one of those, or a combination, then you've set me on the right path.
[14:41] <fastidious> s/anyone/everyone.
[15:34] <MTecknology> dbungert: I finally got around to trying a remote autoinstall ... https://ibin.co/7yhYNAWpmO2F.jpg
[15:39] <MTecknology> The display stuff works fine from a desktop installer, but not so much from the server installer, which it seems is a hard requirement for the autoinstall stuff to work.
[16:12] <athos> Hey everyone; these are our noble FTBFS list: https://pad.riseup.net/p/PQ8p15BOYH5Sg49_A4TE
[17:06] <odc> fastidious: in markdown I would always write: `perl` (the command) and *Perl* (the language)
[17:26] <tsimonq2> athos: I hope my driveby contribution was at least *somewhat* helpful :)
[17:28] <termina> apart from yamllint, is there a good "this cloud-init config won't get loaded by subiquity" lint check that one can do?
[17:32] <cpete> termina: I can't speak for the cloud-init validation, but as long as your config is under the "autoinstall" keyword in the top level cloud config, subiquity should see it
[17:33] <cpete> https://canonical-subiquity.readthedocs-hosted.com/en/latest/tutorial/providing-autoinstall.html
[17:33] <cpete> ^ for some details if you haven't seen it already
[17:33] <athos> thanks, tsimonq2 :)
[17:37] <blackboxsw> termina: if you are on a system w/ cloud-init installed, you can right `cloud-init schema --config-file <your_yaml_file>` can also tell you specifically if there are keys/values that don't adhere to cloud-init's schema definitions.  If running within the live installers(subiquity ephemeral environment) one could run `sudo cloud-init schema --system` to see if cloud-init found the userdata provided to the installer.
[17:37] <termina> ooo, nice! thank you
[17:38] <blackboxsw> `cloud-init query userdata` on the CLI in live installer ephemeral environment should tell you spefically what user-data cloud-init found.
[17:38] <blackboxsw> no prob
[18:04] <ahasenack> TIL
[18:04] <ahasenack> that's handy
[18:04] <ahasenack> I always went looking for the json file somewhere deep in /var/lib
[19:34] <Mmike> where do I ask about ubuntu cloud images? I'm able to boot 'normal' ubuntu-cloud image in KVM, but minimal ubuntu-cloud-image stops with "GRUB_FORCE_UUID set" and then hangs there. 
[20:07] <patdk-lap> mmike is kvm not setting a disk serial or something grub wants for the uuid?