summaryrefslogtreecommitdiffstats
path: root/recipes-core
Commit message (Collapse)AuthorAgeFilesLines
* packagegroup-container: Fix docker typoTheodore A. Roth2025-04-091-1/+1
| | | | | | Signed-off-by: Theodore A. Roth <troth@openavr.org> Signed-off-by: Theodore A. Roth <theodore_roth@trimble.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* metadata: add whitespace around assignmentsMartin Jansa2025-04-031-2/+2
| | | | | | | | | | With: https://lists.openembedded.org/g/bitbake-devel/message/17508 there are many WARNINGs from this layer will cover src_uri.inc files in next commit. Signed-off-by: Martin Jansa <martin.jansa@gmail.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* packagegroup-container: respect seccomp in DISTRO_FEATURESMartin Jansa2024-11-211-3/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * fix f53b101d455d7e7447fa83f2faecb5e05d595b3e * you might want to skip whole packagegroup-netavark without seccomp, but without this parsing world in DISTRO without seccomp fails with: ERROR: Nothing RPROVIDES 'netavark' (but meta-virtualization/recipes-core/packagegroups/packagegroup-container.bb RDEPENDS on or otherwise requires it) netavark was skipped: missing required distro feature 'seccomp' (not in DISTRO_FEATURES) NOTE: Runtime target 'netavark' is unbuildable, removing... Missing or unbuildable dependency chain was: ['netavark'] ERROR: Nothing RPROVIDES 'packagegroup-docker' (but meta-virtualization/recipes-core/packagegroups/packagegroup-container.bb RDEPENDS on or otherwise requires it) No eligible RPROVIDERs exist for 'packagegroup-docker' NOTE: Runtime target 'packagegroup-docker' is unbuildable, removing... Missing or unbuildable dependency chain was: ['packagegroup-docker'] ERROR: Nothing RPROVIDES 'packagegroup-oci' (but meta-virtualization/recipes-core/packagegroups/packagegroup-container.bb RDEPENDS on or otherwise requires it) No eligible RPROVIDERs exist for 'packagegroup-oci' NOTE: Runtime target 'packagegroup-oci' is unbuildable, removing... Missing or unbuildable dependency chain was: ['packagegroup-oci'] ERROR: Nothing RPROVIDES 'packagegroup-container' (but meta-virtualization/recipes-core/packagegroups/packagegroup-container.bb RDEPENDS on or otherwise requires it) No eligible RPROVIDERs exist for 'packagegroup-container' NOTE: Runtime target 'packagegroup-container' is unbuildable, removing... Missing or unbuildable dependency chain was: ['packagegroup-container'] ERROR: Nothing RPROVIDES 'packagegroup-lxc' (but meta-virtualization/recipes-core/packagegroups/packagegroup-container.bb RDEPENDS on or otherwise requires it) No eligible RPROVIDERs exist for 'packagegroup-lxc' NOTE: Runtime target 'packagegroup-lxc' is unbuildable, removing... Missing or unbuildable dependency chain was: ['packagegroup-lxc'] ERROR: Nothing RPROVIDES 'packagegroup-cni' (but meta-virtualization/recipes-core/packagegroups/packagegroup-container.bb RDEPENDS on or otherwise requires it) No eligible RPROVIDERs exist for 'packagegroup-cni' NOTE: Runtime target 'packagegroup-cni' is unbuildable, removing... Missing or unbuildable dependency chain was: ['packagegroup-cni'] ERROR: Nothing RPROVIDES 'aardvark-dns' (but meta-virtualization/recipes-core/packagegroups/packagegroup-container.bb RDEPENDS on or otherwise requires it) aardvark-dns was skipped: missing required distro feature 'seccomp' (not in DISTRO_FEATURES) NOTE: Runtime target 'aardvark-dns' is unbuildable, removing... Missing or unbuildable dependency chain was: ['aardvark-dns'] ERROR: Nothing RPROVIDES 'conmon' (but meta-virtualization/recipes-core/packagegroups/packagegroup-container.bb RDEPENDS on or otherwise requires it) conmon was skipped: missing required distro feature 'seccomp' (not in DISTRO_FEATURES) NOTE: Runtime target 'conmon' is unbuildable, removing... Missing or unbuildable dependency chain was: ['conmon'] Signed-off-by: Martin Jansa <martin.jansa@gmail.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* packagegroups: add iproute, iptables and tiniBruce Ashfield2024-11-151-0/+3
| | | | | | | | | As it turns out CNI needs iptables to configure some plugins, and without it we get a silent fail. It will also be added to the recipe as a RRECOMMENDS, but we also put it in the packagegroup for more visibility. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* packagegroups: add support utilities to cni and containerdBruce Ashfield2024-11-151-0/+5
| | | | | | | When debugging or configuration networking for CNI and containerd we should ensure that support utilties are present. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* packagegroups: add new container package setsBruce Ashfield2024-11-151-1/+21
| | | | | | | | | | Adding the following new pacakge groups: packagegroup-cni packagegroup-netavark packagegroup-container-tools Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* packagegroups: add cri-tools to kubernetesBruce Ashfield2024-11-151-0/+1
| | | | | | | | | | cri-tools aims to provide a series of debugging and validation tools for Kubelet CRI, which includes: crictl: CLI for kubelet CRI. critest: validation test suites for kubelet CRI. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* lxc: don't allow named listening IPv6 address on lxcbrX network interfaceXiangyu Chen2024-11-021-1/+1
| | | | | | | | | | | | | | lxc-net enabled the IPv6 by default since v6.0.0[1], when named enabled on system, the lxc-net which based on dnsmasq would fail to bind the IPv6 address on lxcbrX interface, that cause lxc cannot work correctly. Add the lxc-net default v6 address to named.conf.option to tell named don't bind and listen that address. [1] https://github.com/lxc/lxc/commit/e8888344 Signed-off-by: Xiangyu Chen <xiangyu.chen@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* runv: drop recipeBruce Ashfield2024-05-291-87/+0
| | | | | | | runv is no longer used, kata containers is the suggested VM backed container interface. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* runv: use destsuffix for cloneBruce Ashfield2024-05-291-1/+1
| | | | | | | | | | To ensure that the go code can be unpacked and the license file found, we add destsuffix to the SRC_URI. We still have a gcc14 build issue, but this at least gets us to that issue. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* sysvinit-inittab: Use UNPACKDIR instead of WORKDIRRichard Purdie2024-05-131-1/+1
| | | | | | | | | Now that UNPACKDIR has been introduced to OE-Core, use it in the do_install fuction so that as/when things move around and UNPACKDIR is no longer WORKDIR, it continues to work correctly. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* libvirtd: don't allow named.service listening on libvirt network interfaceXiangyu Chen2024-03-151-2/+2
| | | | | | | | | | | libvirtd has its own network interface named virbr0, and it using dnsmasq to setup the DNS. the named.service also listen interface and try to bind the port 59 on virtbr0, that cause dnsmasq report following error: dnsmasq: failed to create listening socket for 192.168.122.1: Address already in use Signed-off-by: Xiangyu Chen <xiangyu.chen@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* runv: set COMPATIBLE_HOSTKai Kang2023-11-061-0/+6
| | | | | | | runv rdepends on qemu, so update COMPATIBLE_HOST for runv to accord with qemu. Signed-off-by: Kai Kang <kai.kang@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* packagegroup-container: require ipv6 for podmanJörg Sommer2023-11-061-1/+1
| | | | | | | | | | | | | | | | The recipe *podman* requires the distro feature *ipv6*. Using a distro without it causes the build of *packagegroup-container* fails, even if *packagegroup-podman* is not used: ERROR: Nothing RPROVIDES 'podman' (but /build/../work/layers-3rdparty/meta-virtualization/recipes-core/packagegroups/packagegroup-container.bb RDEPENDS on or otherwise requires it) podman was skipped: missing required distro feature 'ipv6' (not in DISTRO_FEATURES) NOTE: Runtime target 'podman' is unbuildable, removing... Missing or unbuildable dependency chain was: ['podman'] NOTE: Runtime target 'packagegroup-docker' is unbuildable, removing... Missing or unbuildable dependency chain was: ['packagegroup-docker', 'podman'] Signed-off-by: Jörg Sommer <joerg.sommer@navimatix.de> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* packagegroup-kubernetes: set COMPATIBLE_HOSTKai Kang2023-09-151-1/+1
| | | | | | | | | packagegroup-kubernetes requires kubernetes which is only compatible with x86_64, arm and aarch64, so set COMPATIBLE_HOST for packagegroup-kubernetes to align with it. Signed-off-by: Kai Kang <kai.kang@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* packagegroup-container: not compatible with mips and riscvKai Kang2023-09-151-1/+1
| | | | | | | | | | The recipe docker-moby which is required by packagegroup-container is not compatible with mips. And it inherits goarch.bbclass, so it is not compatible with riscv32 too. Update COMPATIBLE_HOST accordingly for packagegroup-container. Signed-off-by: Kai Kang <kai.kang@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* oci-image-tools: don't build for riscv64Changqing Li2023-09-042-0/+4
| | | | | | | | | | | | | | | | Currently oci-image-tools has a do_compile error for riscv64. The problem could be reproduced by: MACHINE=qemuriscv64 bitbake oci-image-tools So explicitly set COMPATIBLE_HOST here to avoid it building for riscv64. When someone interested in using this recipe for riscv64 fixes the compile issue, this setting could be removed. Also don't build packagegroup-container/packagegroup-kubernetes since they depends on oci-image-tools Signed-off-by: Changqing Li <changqing.li@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* busybox-initrd: auto pv from busyboxAdrian Freihofer2023-05-171-0/+14
| | | | | | | | | | | | | | | Not hardcoding the version of busybox from the core layer in this layer is a small improvement for maintenance. But the main motivation is to support the following layer combination without getting a parse error from bitbake: - poky LTS, branch = kirkstone - meta-lts-mixins, branch = kirkstone/go - meta-lts-mixins, branch = kirkstone/rust - meta-virtualization, branch = master Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* busybox-initrd: update includeBruce Ashfield2023-01-311-0/+0
| | | | | | | OEcore has an update to busybox, and since we include the core recipe directly, we have to update our PV to match. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* treewide: bulk update patches with status fieldBruce Ashfield2023-01-274-0/+8
| | | | | | | | | | | | | | | While the insane.bbclass upstream-status check hasn't been made default, users of meta-virtualization may have it enabled in their distros .. so the effect is the same. We must have this tracking tag in out patches. This is a bulk update to add the tag and silence the QA message. As packages get updated, the normal/routine process of checking the patches will continue, and the status fields may (or may not) get more useful. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* xen/sysvinit: add hvc0 console only if not there alreadyBertrand Marquis2022-07-071-2/+8
| | | | | | | | | | | | | | The base inittab recipe is creating inittab entries for consoles listed in SERIAL_CONSOLES. For qemu, this contains "115200,hvc0" so an entry is created in inittab for it. Prevent to create a second entry if hvc0 is present in SERIAL_CONSOLES. On qemuarm, this solves issues with the console when starting on top of Xen as dom0. Signed-off-by: Bertrand Marquis <bertrand.marquis@arm.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* kata-containers: add skip messageBruce Ashfield2022-06-034-0/+9
| | | | | | | Let's skip these until someone is interested enough to fix the recipes. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* kata-containers: add protocol=https to SRC_URIsBruce Ashfield2022-06-034-5/+5
| | | | | | | | | | | Although the components of kata containers aren't functional, we keep it around in case someone is interested in fixing the recipe. It was skipped from the global protocol=https addition for that reason .. but in case someone is running global/world fetches, this can cause a problem. So we add the missing procotol specification. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* busybox-initrd: update to 1.35.0Bruce Ashfield2022-01-111-0/+0
| | | | | | | OE core commit a7d5150b621c2ab4e4 has bumped busybox to 1.35.0, so we update our initrd recipe accordingly. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* kubernetes: install kubeadm and misc for nodesBruce Ashfield2021-12-151-0/+2
| | | | | | | To ensure nodes can join the cluster, and have the proper configuration of some kernel options we add two more packages to the packagegroup Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* k8s: add kubernetes to host packagegroupBruce Ashfield2021-12-131-0/+1
| | | | | | | Install the core kubernetes package (and RDEPENDS) as part of the host packagegroup. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* global: convert github SRC_URIs to use https protocolBruce Ashfield2021-11-022-2/+2
| | | | | | | | | | | github is removing git:// access, and fetches will start experiencing interruptions in service, and eventually will fail completely. bitbake will also begin to warn on github src_uri's that don't use https. So we convert the meta-virt instances to use protocol=https (done using the oe-core contrib conversion script) Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* global: add explicit branch to all SRC_URIsBruce Ashfield2021-11-024-4/+4
| | | | | | | | | | | | | | As introduced in the oe-core post: https://lists.openembedded.org/g/openembedded-core/message/157623 SRC_URIs without an explicit branch will generate warnings, and eventually be an error. We run the provided conversion script to make sure that meta-virt is ready for the change. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* busybox-initrd: update version to match oe-coreBruce Ashfield2021-10-111-0/+0
| | | | | | | OEcore has moved to 1.34.1 of busybox, so we do the same with our initrd recipe. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* virtual/containerd: don't rprovide virtual/Bruce Ashfield2021-09-061-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Similar to the oe-core commit: commit 93ac180d8c389f16964bce8bd5538d9389e970e6 Author: Michael Opdenacker <michael.opdenacker@bootlin.com> Date: Wed Sep 1 11:20:20 2021 +0200 meta: stop using "virtual/" in RPROVIDES and RDEPENDS Fixes [YOCTO #14538] Recipes shouldn't use the "virtual/" string in RPROVIDES and RDEPENDS. That's confusing because "virtual/" has no special meaning in RPROVIDES and RDEPENDS (unlike in PROVIDES and DEPENDS). Instead, using "virtual-" instead of "virtual/" as already done in the glibc recipe. We stop rproviding virtual/containerd to keep the namespace clean. There aren't many users of this virtual provides, but we keep it around (for now) to maintain compatibility. At the same time we convert the RPROVIDES to virtual-containerd, to keep it available and consistent with oe-core use virtual-libc, etc. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* virtual/runc: don't rprovide virtual/Bruce Ashfield2021-09-061-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Similar to the oe-core commit: commit 93ac180d8c389f16964bce8bd5538d9389e970e6 Author: Michael Opdenacker <michael.opdenacker@bootlin.com> Date: Wed Sep 1 11:20:20 2021 +0200 meta: stop using "virtual/" in RPROVIDES and RDEPENDS Fixes [YOCTO #14538] Recipes shouldn't use the "virtual/" string in RPROVIDES and RDEPENDS. That's confusing because "virtual/" has no special meaning in RPROVIDES and RDEPENDS (unlike in PROVIDES and DEPENDS). Instead, using "virtual-" instead of "virtual/" as already done in the glibc recipe. We stop rproviding virtual/runc to keep the namespace clean. There aren't many users of this virtual provides, but we keep it around (for now) to maintain compatibility. At the same time we convert the RPROVIDES to virtual-runc, to keep it available and consistent with oe-core use virtual-libc, etc. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* busybox-initrd: rename to match 1.34.0 version from oe-coreMartin Jansa2021-08-271-0/+0
| | | | | | | | Upgraded in: https://git.openembedded.org/openembedded-core/commit/?id=d0e694ef4ec7bd862bdefee494210e3878152b44 Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* global: overrides syntax conversionBruce Ashfield2021-08-0216-38/+38
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | OEcore/bitbake are moving to use the clearer ":" as an overrides separator. This is pass one of updating the meta-virt recipes to use that syntax. This has only been minimally build/runtime tested, more changes will be required for missed overrides, or incorrect conversions Note: A recent bitbake is required: commit 75fad23fc06c008a03414a1fc288a8614c6af9ca Author: Richard Purdie <richard.purdie@linuxfoundation.org> Date: Sun Jul 18 12:59:15 2021 +0100 bitbake: data_smart/parse: Allow ':' characters in variable/function names It is becomming increasingly clear we need to find a way to show what is/is not an override in our syntax. We need to do this in a way which is clear to users, readable and in a way we can transition to. The most effective way I've found to this is to use the ":" charater to directly replace "_" where an override is being specified. This includes "append", "prepend" and "remove" which are effectively special override directives. This patch simply adds the character to the parser so bitbake accepts the value but maps it back to "_" internally so there is no behaviour change. This change is simple enough it could potentially be backported to older version of bitbake meaning layers using the new syntax/markup could work with older releases. Even if other no other changes are accepted at this time and we don't backport, it does set us on a path where at some point in future we could require a more explict syntax. I've tested this patch by converting oe-core/meta-yocto to the new syntax for overrides (9000+ changes) and then seeing that builds continue to work with this patch. (Bitbake rev: 0dbbb4547cb2570d2ce607e9a53459df3c0ac284) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* packagegroup-container: Include podman if seccomp is in DISTRO_FEATURESDiego Sueiro2021-06-301-1/+2
| | | | | Signed-off-by: Diego Sueiro <diego.sueiro@arm.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* initrd: bump busybox to 1.33.1 to match oe-corezhengruoqin2021-05-111-0/+0
| | | | | | | OE core has updated busybox, so we bump to match. Signed-off-by: Zheng Ruoqin <zhengrq.fnst@cn.fujitsu.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* packages: drop libseccomp checks / package blacklistBruce Ashfield2021-04-261-1/+0
| | | | | | | | libseccomp has moved to oe-core, so we can drop our checks and blacklisting of packages if meta-security is not in the layer configuration. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* sysvinit: make all modifications conditional on virtualization distro featureBruce Ashfield2021-04-262-10/+10
| | | | | | | | | | To ensure yocto compatibility, we should not be changing the behaviour of recipes simply when meta-virt is included. As such, we change our sysvinit-inittab changes to only trigger when virtualization is in the distro features. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* busybox: Add nsenter for podman runtimeNathan Dunne2021-04-182-0/+2
| | | | | | | Add nsenter to Busybox configuration as it is required by Podman at runtime Signed-off-by: Nathan Dunne <Nathan.Dunne@arm.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* cri-o, podman, packagegroup-container: replace anonymous python function ↵Martin Jansa2021-04-061-9/+1
| | | | | | | | | | calling bb.parse.SkipRecipe with conditional PNBLACKLISTs * PNBLACKLISTs are IMHO a bit easier to read and easier to override from distro which e.g. provides own recipe for libseccomp Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* packagegroup-container: skip without meta-security because of podmanMartin Jansa2021-04-061-0/+9
| | | | | | | | * copy the skip from podman recipe, because this packagegroup depends on podman Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* packagegroup-kubernets: add seccomp to REQUIRED_DISTRO_FEATURESMartin Jansa2021-04-061-0/+4
| | | | | | | | | | | | | * fixes world build: ERROR: Nothing RPROVIDES 'k3s-server' (but meta-virtualization/recipes-core/packagegroups/packagegroup-kubernetes.bb RDEPENDS on or otherwise requires it) k3s RPROVIDES k3s-server but was skipped: missing required distro feature 'seccomp' (not in DISTRO_FEATURES) NOTE: Runtime target 'k3s-server' is unbuildable, removing... Missing or unbuildable dependency chain was: ['k3s-server'] ERROR: Required build target 'meta-world-pkgdata' has no buildable providers. Missing or unbuildable dependency chain was: ['meta-world-pkgdata', 'packagegroup-kubernetes', 'k3s-server'] Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* runx: update to v1.0Bruce Ashfield2021-03-267-1703/+87
| | | | | | | | | | bumping runX to the 1.0 tag - drop patches that are part of the release - bump kernel to v5.4.104 to work with our gcc10 - tweak initrd install to use externally provided busybox Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* containers: add a base container and kubernetes base packagegroupBruce Ashfield2021-03-152-0/+86
| | | | | | | | To make it easier to build container host or k*s host images (as well as guests), we start to add some packagegroups that wrap the required elements. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* initrd: bump busybox to 1.33 to match oe-coreBruce Ashfield2021-02-261-0/+0
| | | | | | OE core has updated busybox, so we bump to match. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* containers: add a dummy provider for /bin/sh and /bin/envBruce Ashfield2020-11-051-0/+6
| | | | | | | | | | | | | | | | | | | | | | In some scenarios (and package managers), packages post install scripts may have references to /bin/sh. The package manager doesn't know if the scripts will run on the build host or target, so we get a calculated redepnds on /bin/sh base-files and base-passwd fall into this category of having post installs, but no need for /bin/sh on the target. If you know what you are installing, and want the smallest container possible, this package will satisfy the dependency when assembling the rootfs. To enable it, put the following in a configuration file (local.conf or otherwise): PACKAGE_EXTRA_ARCHS_append = " container-dummy-provides" Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* kata: cleanup runtime recipeBruce Ashfield2020-10-082-10/+37
| | | | | | | | | | | Some of the dependencies are no longer valid for the kata runtime recipe. This also drops hyperstart as a dependency. With this removal, we need a replacement kernel and initrd for kata. That replacement will happen in future commits. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* busybox-initrd: move static configuration to 'vmsep' distro featureBruce Ashfield2020-09-283-2/+2
| | | | | | | | | | | We already have a distro feature that controls the static/non-static configuration of libgcrypt: 'vmsep' To avoid build errors on distros that don't have static libgcrypt available, we move the CONFIG_STATIC config to a fragment and only enable it whent he distro feature is set. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* runx: allow internal and external busyboxBruce Ashfield2020-09-223-5/+1645
| | | | | | | | runx knows how to build its own copy of busybox for its initrd, adding a flag to allow us to select which mode we want. Signed-off-by: Bruce Ashfield <bruce.ashfield@xilinx.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* runx: robustness changesBruce Ashfield2020-09-222-3/+38
| | | | | | | | | | | | | Adding one build and one runtime robustness change: - build: specify the syroot native as a library path to qemu user. This allows us to run dynamic executables - runtime: add a patch to increase the serial fd timeout. We'll drop this once it is merged upstream. Signed-off-by: Bruce Ashfield <bruce.ashfield@xilinx.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* busybox: add initrd variantBruce Ashfield2020-09-223-0/+35
| | | | | | | | | | | | | | | | Add a busybox variant that inherits almost all of its support from the core busybox recipe, but adds configuration values that are appropriate to be used in an initrd. In particular: - we build busybox statically - we enable runlevel and init functionality - mdev is always enabled - applet install support is enabled Signed-off-by: Bruce Ashfield <bruce.ashfield@xilinx.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-05-13 18:12:32 +0000