**** BEGIN LOGGING AT Sun Feb 21 02:59:58 2021 Feb 21 06:17:15 smurray: I've successfully built core-image-minimal with IMAGE_FSTYPES = "container" with bare minimum. I've nailed the problem down to my distro. Switching to poky does compile a container image, so my distro (not based on poky) clearly misses some lines to make the "container" type work. Feb 21 12:25:28 JPEW, kanavin: I think diffoscope is partly so slow on the autobuilder as its running on NFS. Could we run diffoscope on a local copy of the packages instead of in the saved output dir? Feb 21 14:53:26 Hello. if I have "bz2"  file after building, should I flash that file or should I decompress it first? Feb 21 15:09:44 RP: I guess JPEW is better equipped to answer this, as he wrote the code :) Feb 21 15:17:32 kanavin: probably, just wondered if one of you wanted to tweak it :) Feb 21 15:18:16 kanavin, JPEW: I'm very slowly picking off some of the reproducibility issues. I'm also rather depressed with some of the patches we're carrying, some are quite scary/shocking :( Feb 21 15:20:10 I am having a hard time with kernel modules. If I build them in the kernel (=y), then it's fine, but when I have them as module (=m), they don't seem to get on my image. I tried to add the following to my machine `*.conf`, and I would expect it to fail at build time, but it doesn't: `MACHINE_EXTRA_RDEPENDS += "kernel-module-foo"` Feb 21 15:21:33 jonesv[m]: a lot would depend on whether the image you're using uses that variable Feb 21 15:21:47 jonesv[m]: did you try adding to IMAGE_INSTALL directly? Feb 21 15:21:57 (Just to rule that out) Feb 21 15:22:42 aha, I am using my own small image on top of core-minimal. Let me read about IMAGE_INSTALL, not sure how to use it Feb 21 15:23:07 jonesv[m]: I'd guess minimal is being very minimal and not including those dependencies Feb 21 15:23:52 RP: also, where can I find a list of kernel-modules that exist as packages in Yocto? I want a usb gadget, and I would like to `modprobe u_ether` for instance, but I would need to see if a package called `kernel-module-u-ether` exists and install it, right? Feb 21 15:24:31 jonesv[m]: have a look in tmp/deploy// Feb 21 15:24:32 But shouldn't `MACHINE_EXTRA_RDEPENDS` tell it to include them? Feb 21 15:24:56 jonesv[m]: minimal image behaves a little differently to the other images Feb 21 15:25:13 jonesv[m]: I think that is why MACHINE_ESSENTIAL_EXTRA_RDEPENDS exists Feb 21 15:25:24 jonesv[m]: you could try adding to that Feb 21 15:26:13 right. Let me first try with IMAGE_INSTALL in my image recipe :) Feb 21 15:26:51 jonesv[m]: IMAGE_INSTALL_append = " kernel-module-foo" Feb 21 15:26:58 note the space Feb 21 15:38:23 RP: so I added `kernel-module-g-ether` to `IMAGE_INSTALL`, built the image, and now I don't find it in `/lib/modules/5.4.58-yocto-standard/`... but that's where it should be, right? Feb 21 15:39:12 `$ lsmod` says "Not tainted", so I assume that I have no module loaded Feb 21 15:39:43 * jonesv[m] sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/HxBExImBnUZtCVaLsHHepzWh/message.txt > Feb 21 15:40:27 I think there is really something I'm missing with kernel modules 😕. Maybe I should stay with `(=y)` and give up with them, but I would like to understand how it's supposed to work Feb 21 15:49:42 BTW RP : what did you mean with "minimal image behaves a little differently to the other images"? Where could I see what it doesn't do that "other images" do? Feb 21 15:56:04 aha! I needed to add `kernel-module-g-ether kernel-module-usb-f-eem` to `IMAGE_INSTALL`, and now I can `modprobe g_ether` and it creates a new network interface 🎉. Now I need to understand where I should actually add those two packages (probably not in `IMAGE_INSTALL`, looking into `MACHINE_ESSENTIAL_EXTRA_RDEPENDS`) Feb 21 15:59:37 Ok I got it: Feb 21 17:32:36 What distro (or machine?) features does the "container" IMAGE_FSTYPES require? I can compile a container image on poky but not on my poky-less distro. What could I be missing? Feb 21 17:47:06 RP: I hope none of those ugly patches carry my name :) can you point to some particularly bad examples? Feb 21 17:47:12 err, 'good' examples Feb 21 17:47:16 notable examples :D Feb 21 17:47:26 interesting examples! Feb 21 17:59:31 example examples Feb 21 18:05:23 zeddii: that perhaps will be good way to go Feb 21 19:02:51 does linux-dummy prevents compiling the bootloader? Feb 21 19:31:18 vdl: I suspect it's not linux-dummy per se, but rather the minimal dependencies that the container image class has resulting in it not being a dependency Feb 21 19:31:50 vdl: the assumption is a "container" image does not boot, hence no bootloader Feb 21 19:33:01 smurray: yeah for the bootloader question I was wondering if I must set the preferred virtual/bootloader to dummy or something (similar to linux-dummy) Feb 21 19:34:18 vdl: I've never seen that required in my use of it Feb 21 19:34:52 vdl: but that's mostly been relatively simple things Feb 21 19:37:53 smurray: I'm creating a foo-dummy machine to specify IMAGE_FSTYPES = "container", PREFERRED_PROVIDER_virtual/kernel = "linux-dummy", and IMAGE_INSTALL_remove = "kernel-devicetree". I guess such dedicated machine definition is the proper way to specify the hardware to build a container image for, correct? Feb 21 19:39:23 vdl: it's definitely one way, I've done it for some of my container examples for talks on it Feb 21 19:41:25 vdl: in a multiconfig setup, it could be potentially done in the multiconfig conf file instead of carrying an extra machine definition just for that Feb 21 19:42:23 I see Feb 21 19:42:45 kind of depends what you think is easier wrt maintenance Feb 21 19:43:34 I'm still struggling to understand the difference between having two kas files (assuming you're using kas) and a multiconfig. I guess the thing with multiconfig is that you can e.g. embedded configA.tar.xz into configB.wic for example, is that correct? Feb 21 19:46:00 vdl: yes Feb 21 19:46:25 smurray: in my case it's actually a good thing to separate the generic hardware architecture from the board details (dts and such), so foo-dummy sounds reasonable Feb 21 20:45:48 how can I set the full image link name to "sdcard.img"? Feb 21 20:58:36 smurray: actually can an image recipe set PREFERRED_PROVIDER_virtual/kernel? That seems odd. Feb 21 21:17:50 vdl: in general no, since it's global configuration used by multiple recipes Feb 21 21:18:43 vdl: it might happen to work with something like a specific build of a container image recipe that did it, but it'd be fragile Feb 21 21:49:27 thank you Feb 21 21:52:20 dl9pf: https://autobuilder.yoctoproject.org/typhoon/#/builders/52/builds/3070 - don't understand why we're getting those warnings yet but they're from the SDE patch :( Feb 21 21:52:27 kanavin: don't think any have your name :) Feb 22 02:00:40 RP: We can run diffoscope on local files if that would help Feb 22 02:01:54 RP: Yes, our concept of "reproducible" is a little stricter than reproducible-builds.org in some ways, so we end up with a few gnarly things. I suspect they are mostly path related patches? **** ENDING LOGGING AT Mon Feb 22 02:59:57 2021