Wrong mailing list. Use meta-virtualization for these patches. I'm cross posting this there, for the archives. I've grabbed and merged this change (but could easily have missed it, since it was the wr

Check the list. It never came through. You need to be a subscriber and would have received a bounce message. I know that, since I got the bounce as the list admin :D Bruce

This should go to the linux-yocto list, since that's where people interested in the linux-yocto kernel variants will notice it. In this case, there was a bad merge. If you check the preempt-rt branche

Yep. You can specify routines like that. You just need to get the content and ordering right to do what you want. Bruce

Thanks for the layers and cut & paste instructions. They helped a lot. .. even with that start, it took me a bit to figure things out. In the end, I can't actually figure out how to get the fragment w

Thanks Greg, I was able to reproduce the problem a few minutes ago, but will have to look at the root cause in the morning! Bruce

I can't tell from the information provided. But if you can send me a set of layers to clone, and configure locally, I can figure it out. Cheers, Bruce

This is not necessarily true. It would be better stated that if you are modifying the .cfg files in the layer directly, you should list them on the SRC_URI to have the changes picked up by bitbake. It

This should be conditional. I'm not seeing these warnings/errors on any of my builds, so clearly you have a different configuration. Bruce

These are all to the wrong mailing list, please resend them to the meta-virtualization list. These need to be 2 separate patches on the resend. Bruce

Nope. This is fully intentional. The defconfig is traditionally a complete .config that specifies all values. As such, we clear the settings with allnoconfig and then apply it to the tree. If you want

4.18 is replacing 4.15 as the latest kernel in the upcoming release, so we drop this dangling bbappend. Signed-off-by: Bruce Ashfield <bruce.ashfield@...> --- .../recipes-kernel/linux/linux-

4.18 will be the newest kernel in the upcoming release, so we bump our default to it in preparation of 4.15 being dropped. Signed-off-by: Bruce Ashfield <bruce.ashfield@...> --- meta-poky/co

4.18 will be the newest kernel in the upcoming release, so we bump our default to it in preparation of 4.15 being dropped. Signed-off-by: Bruce Ashfield <bruce.ashfield@...> --- meta-poky/co

check on the meta-virtualization list. We already have lxc and the support tools, and lxd has been discussed there in the past. So asking there, will find you someone that may already have a recipe or

I can help with this ... but first, is this a configuration that I can build myself ? i.e. what branch, what layers and what extra configs would I need ? Bruce

I'm going to hold onto this one a bit longer. We have specific version requirements and will revisit when the next openstack uprev is done. Cheers, Bruce

Great news. I was about to do another run of this, and still will, but this is good to know. Definitely let us know what breaks next :D Bruce

I double checked over the weekend, and I have no problems with linux-yocto + the meta-virtualization fragment and docker. Did you say that you confirmed on target via /proc/config.gz that all the opti

Make sure to cc meta-virtualization on questions like this, since that is where you'll get more eyes that are running docker all the time. I've never seen that wiki page before (or at least I don't re