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). Bruce > Additionally, I added VIRTUAL-RUNTIME_container_orchestration = "k8s", > but it didn't help. > > Thanks, > Ramon > > > -- - 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 (#8793): https://lists.yoctoproject.org/g/meta-virtualization/message/8793 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]] -=-=-=-=-=-=-=-=-=-=-=-
