On Mon, Jun 10, 2024 at 10:56 PM Bruce Ashfield <[email protected]> wrote: > > On Mon, Jun 10, 2024 at 12:22 AM Ramon Fried <[email protected]> wrote: > > > > On Mon, Jun 10, 2024 at 6:01 AM Bruce Ashfield <[email protected]> > > wrote: > > > > > > On Sat, Jun 8, 2024 at 5:15 PM Ramon Fried via lists.yoctoproject.org > > > <[email protected]> wrote: > > > > > > > > Hi. > > > > On mickledore, when directly selecting kubernetes, only k8s is built. > > > > I recently noticed the packagegroup-kubernetes-node and decided to use > > > > that instead of kubernetes. > > > > When Iuse that, we see k3s is also pulled and built. > > > > > > > > I masked the k3s.bb to understand the dependencies and it looks like > > > > that: > > > > > > > > Missing or unbuildable dependency chain was: ['k3s-server'] > > > > NOTE: Runtime target 'packagegroup-k8s-node' is unbuildable, removing... > > > > Missing or unbuildable dependency chain was: ['packagegroup-k8s-node', > > > > 'k3s-server'] > > > > NOTE: Runtime target 'packagegroup-core-boot' is unbuildable, > > > > removing... > > > > Missing or unbuildable dependency chain was: > > > > ['packagegroup-core-boot', 'packagegroup-k8s-node', 'k3s-server'] > > > > NOTE: Runtime target 'core-image-minimal' is unbuildable, removing... > > > > Missing or unbuildable dependency chain was: ['core-image-minimal', > > > > 'packagegroup-core-boot', 'packagegroup-k8s-node', 'k3s-server'] > > > > > > > > Is it intentional, or is there a problem here ? > > > > > > > > > > It's more the way that packagegroups work. > > > > > > How are you building packagegroup-k8s-node ? is it from your own > > > image (and rdepends) ? or is it from the command line on bitbake > > > (which shouldn't work as it is only rprovided). > > Building the complete image. The packagegroup was added to > > MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS. > > As a follow up, are you seeing it built and installed, or just built ? > > I'm assuming that it is just being built, and that is due to the nature > of the packagegroups, where everything that might be provided by > the packagegroup is built, but obviously not installed. > > Since the packagegrooup has mainly been used for build coverage > testing, with the rprovided packagegroups being used for installation > and runtime testing. > > I wouldn't object to splitting the packagegroups up a bit more to > avoid the extra building, but I just haven't had time to get around > to doing it yet. > > Bruce OK. understood. So what packages do I need to pick up manually in order to enable only the kubernetes node ? I'm selecting "kubernetes" but it seems that it pulls too much also with selecting "kubernetes" Thanks, Ramon. > > > Bruce > > > -- > - Thou shalt not follow the NULL pointer, for chaos and madness await > thee at its end > - "Use the force Harry" - Gandalf, Star Trek II
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#8797): https://lists.yoctoproject.org/g/meta-virtualization/message/8797 Mute This Topic: https://lists.yoctoproject.org/mt/106566745/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/meta-virtualization/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
