summaryrefslogtreecommitdiffstats
path: root/recipes-containers/singularity
Commit message (Collapse)AuthorAgeFilesLines
* containers: adapt to UNPACKDIR changesBruce Ashfield2025-06-251-2/+0
| | | | | | | | | | | | | This commit updates the container recipes to the OE core UNPACKDIR changes. - We drop references to WORKDIR - We adjust destsuffix fetches to use BB_GIT_DEFAULT_DESTSUFFIX instead of 'git' - Update our GOPATH references to use UNPACKDIR - Drop S = assignemnts where possible Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* recipes/classes/scripts: Drop SRCPV usageBruce Ashfield2023-08-241-1/+1
| | | | | | | | | bitbake has been enhanced such that SRCPV is no longer needed in PV to handle updating git hashes and task signatures. We can simplify our PV by dropping SRCPV Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* treewide: bulk update patches with status fieldBruce Ashfield2023-01-272-0/+4
| | | | | | | | | | | | | | | 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>
* singularity: Drop explicit runtime dep glibcAndrei Gherzan2022-08-201-1/+1
| | | | | | | | There is no need we can see for this dependency to be provided as such - especially forcing this to using glibc. Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* singularity: fix build with automake-1.16.5Martin Jansa2021-11-302-0/+35
| | | | | Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* global: add explicit branch to all SRC_URIsBruce Ashfield2021-11-021-1/+1
| | | | | | | | | | | | | | 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>
* singularity: update generic "BSD" license specificationBruce Ashfield2021-09-161-1/+1
| | | | | | | | Although singularity is somewhat broken, the LICENSE was not precisely set, so we update the field to indicate that it is BSD clause 3 or Apache 2 licensed. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* global: overrides syntax conversionBruce Ashfield2021-08-021-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* singularity: fix build with python3Martin Jansa2020-05-212-9/+151
| | | | | | | | | | | | | | | | | | * Fix python3native inherit added in: https://git.yoctoproject.org/cgit/cgit.cgi/meta-virtualization/commit/?id=a1e3f5c92cdee7c4259b7be643bd829ce7c1efa3 to actually work * also remove the work arounds for /usr/bin/python being python3 on the target device * I haven't tested this in runtime - I don't use it, it was just showing that do_configure error in "bitbake world" builds, the scripts might need some changes to be really compatible with python3, but it was broken already, now it at least builds * upgrade to new version with https://github.com/hpcng/singularity/pull/1762/commits/3c05f06e6a1c490a4b4714bcdf5a0ce2b2498bb5 would be nice by someone who actually uses this Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* singularity: update for python3 supportBruce Ashfield2020-01-221-1/+1
| | | | Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* singularity: openssl cert configs path fixed.Cevat Bostancioglu2019-07-031-2/+2
| | | | | | openssl recipe moves ssl-1.1 directory as ssl , singularity recipe cannot find ssl-1.1 path. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* singularity: Added dependency to e2fsprogs-mke2fsAlexandru Tiniuc2017-09-051-1/+1
| | | | | | | | | | While the recipe was functional under an image based on core-image- full-cmdline, when tested with core-image-minimal runtime issues appeared: Singularity was unable to create a filesystem within the container. This change fixes this issue. Signed-off-by: Alexandru Tiniuc <tiniuc.alexandru@gmail.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* Added dependency to BashAlexandru Tiniuc2017-08-311-1/+1
| | | | | | | | | If Bash is not included by any other recipe, the recipe fails at the QA check. This commit adds Bash to the list of dependencies, preventing this issue. Signed-off-by: Alexandru Tiniuc <tiniuc.alexandru@gmail.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* Added README fileAlexandru Tiniuc2017-08-291-0/+46
| | | | | Signed-off-by: Alexandru Tiniuc <tiniuc.alexandru@gmail.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* Added recipe for the Singularity container platform.Alexandru Tiniuc2017-08-291-0/+35
Singularity is a container platform built on the principle of mobility of compute. It is designed to be used on HPC clusters and, unlike Docker, it does not require root access to mount an image. In addition, it can use Docker images out-of-the-box and it can pull them from the Docker Hub. For more information, see singularity.lbl.gov This recipe enables building the Singularity container platform. Additionally, it creates a symlink from /usr/bin/python3 to /usr/bin/python, as well as a symlink to where python3 expects CA certificates to be. I have tested it on a Raspberry Pi 3: I successfully built and run arm32v7 images from Docker Hub. Make sure you have the right image for your CPU architecture: it defaults to amd64. Signed-off-by: Alexandru Tiniuc <tiniuc.alexandru at gmail dot com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-07-19 22:32:37 +0000