linux/meta-virtualization.git/recipes-containers/sloci-image, branch master

sloci-image: update to v0.1.2

2026-06-01T13:28:32+00:00

Bumping sloci-image to version v0.1.2, which comprises the following commits: b45be2e Release version 0.1.2 ab128a4 License: Bump year f86399b Readme: Update preamble 056e127 Fix "--arch arm64" argument - don't rewrite it to "arm" 195b540 Replace Travis CI with GitHub Actions 6663693 Don't create top-level directory in tar archive fafbf1f Release version 0.1.1 f2ebd0a Fix escaping issues when generating the OCI image config files 4015e49 Makefile: Declare "install" as PHONY and sort targets Signed-off-by: Bruce Ashfield

containers: adapt to UNPACKDIR changes

2025-06-26T02:40:08+00:00

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

recipes/classes/scripts: Drop SRCPV usage

2023-08-24T01:38:21+00:00

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

treewide: bulk update patches with status field

2023-01-27T15:32:06+00:00

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

global: convert github SRC_URIs to use https protocol

2021-11-02T13:57:03+00:00

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

global: add explicit branch to all SRC_URIs

2021-11-02T13:57:03+00:00

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

sloci-image: allow target and nativesdk variants

2021-05-19T02:42:27+00:00

We now have use cases for sloci that can run on the target itself, or have it used in a nativesdk scenario. To avoid the awkwardly named "nativesdk-sloci-image-native" or .inc files, we rename the recipe sloci-image_git and use BBCLASSEXTEND for native/nativesdk support This is similar to the change sent by: Hongxu Jia , but is updated to the current sloci-image recipe contents. Signed-off-by: Bruce Ashfield

sloci-image: set CLEANBROKEN = 1

2020-09-21T21:31:53+00:00

Workaround rebuild failure Signed-off-by: Hongxu Jia Signed-off-by: Bruce Ashfield

sloci-image: fix variant quoting

2020-07-20T02:26:14+00:00

Bash doesn't deal very well with the quoted "variant" in the output of the oci-image-index. We can calculate the string at the top of the function, and just use it as a whole to avoid needing to figure out the quote escaping. No changes in the output, except a properly quoted "variant" when a variant is defined. We also adjust the definition of "S", since it really wasn't correct before, and now that we have patches, it is more important. Signed-off-by: Bruce Ashfield

containers: introduce sloci for generating OCI image directories

2019-02-27T16:46:25+00:00

There are multiple different tools/techniques to generate OCI images. Many of these techniques are part of more complex workflows, or have many options that are needed as part of a larger system or are needed to provide flexibility in the tooling (i.e. they construct the container as well as build the OCI image, or they can push directly to a registry, etc). What we want within the build context of bitbake/oe is to not duplicate work that is done by bitbake, the other image bbclasses or the runtime part of the ecosystem. This means only the construction of an image-spec v1.x image without dependencies on build, or execution of the container within a tool. We'd also like the tool to not pull in multiple, unused dependencies that must be built native/native-sdk, etc, to support the simple use case. The requirements above exclude (for now) tools such as skopeo, umoci, buildah, img, orca-build, kaniko, scratchbuild, etc. Leading us to a from-scratch implementation .. or enter sloci-image. sloci-image is a simple CLI for packing a rootfs into a single layer OCI image. It can easily be extended, or ported to other language implementations in the future. But it brings nearly no native dependencies and is a pure/clean implementation of the image spec that integrates nicely in an oe/bitbake environment. Signed-off-by: Bruce Ashfield