linux/meta-virtualization.git/conf/layer.conf, branch walnascar

conf/layer.conf: add walnascar compatibility

2025-04-02T02:10:47+00:00

Start the transition from styhead to walnascar by adding the new core layer name as compatible. Once the transition is done, styhead will be removed. Signed-off-by: Bruce Ashfield

conf: add CONTAINER and VIRTUALIZATION PROFILE defaults

2024-11-15T19:50:00+00:00

These are used to set configuration for container and virtualization stacks. We set a default to ensure that sane values are always present. Signed-off-by: Bruce Ashfield

layer: set compatibility to styhead

2024-05-29T13:16:56+00:00

With the recent UNPACKDIR and golang changes, master is only compatible with styhead. Signed-off-by: Bruce Ashfield

containerd: consolidate to "containerd"

2024-05-14T02:32:38+00:00

We no longer need the split between container-docker and containerd-opencontainers and dependent layers have been given over a year to adapt. We do keep the provides and rprovides around for a bit longer, but those will also be removed in the future. Signed-off-by: Bruce Ashfield

conf/layer: add scarthgap compatibility

2024-03-15T17:16:33+00:00

Signed-off-by: Bruce Ashfield

conf: drop mickledore, only specify nanbield

2023-09-15T16:10:00+00:00

- mickledore was incorrectly spelled - we aren't actively going to test both branches with master, so go to only nanbield If there's demaand, and test results to support it, we can reconsider later. Signed-off-by: Bruce Ashfield

conf: update compatibility to match oe-core

2023-09-11T14:38:08+00:00

OE Core has bumped to the next version, we update to match. For now, we keep both mickledore and nanbield as compatible while progressing towards release. Signed-off-by: Bruce Ashfield

layer.conf: use docker-moby as preferred provider

2023-06-07T20:39:24+00:00

docker-ce has been deprecated, so switch to docker-moby as the preferred provider. Signed-off-by: Chen Qi Signed-off-by: Bruce Ashfield

conf: introduce container configuration values

2023-03-08T22:08:02+00:00

From the configuration file itself: These variables represent groupings of functionality in the CNCF landscape. In particular, they are areas where there is a choice between more than one implementation or an area where abstraction is beneficial. The contents of the variables are are runtime components that recipes may use for RDEPENDS. Build dependencies are not typically flexible, so do not currently have DEPENDS equivalents for the components (i.e. DEPENDS on runc versus crun). Distro features such as kubernetes or other container stacks can be used to set different defaults for these variables. Note: these are "global" values, since they represent choices. If more than of a grouping is required on target, then the variable can be appended or set to multiple values. That being said, Recipes should generally agree on the values, hence the global namespace. Recipe specific choices can still be done, but they risk conflicting on target or causing runtime issues / errors. ## CNCF "components" # engines: docker-ce/docker-moby, virtual-containerd, cri-o, podman VIRTUAL-RUNTIME_container_engine ??= "podman" # runtime: runc, crun, runv, runx VIRTUAL-RUNTIME_container_runtime ??= "virtual-runc" # networking: cni, netavark VIRTUAL-RUNTIME_container_networking ??= "cni" # dns: cni, aardvark-dns VIRTUAL-RUNTIME_container_dns ??= "cni" # orchestration: k8s, k3s VIRTUAL-RUNTIME_container_orchestration ??= "k3s" ## Kubernetes terminology "components" VIRTUAL-RUNTIME_cri ??= "containerd" VIRTUAL-RUNTIME_cni ??= "cni" Signed-off-by: Bruce Ashfield

conf: mark layer compatible with mickledore

2023-01-04T01:24:47+00:00

Signed-off-by: Bruce Ashfield