The Xen image recipe provides a default WKS_FILE for x86 builds to enable booting the image either in qemu or directly on hardware. Add settings for WKS_FILE_DEFAULT_DEPENDS that specify the wic image

Signed-off-by: Chen Qi <Qi.Chen@...> --- .../containerd/containerd-opencontainers_git.bb | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/recipes-containers/containerd/contain

I added the meta-virtualization layer to a Yocto (Kirkstone) project using KAS. When I try to compile the project I get the following errors. I was hoping that the layer should build cleanly since I h

Skip the inclusion of the parent directory in the tar file. Most tools expect a tar file without it. An example of this use case is skopeo, where the skopeo copy oci-archive command will not work with

Just letting everyone know that I am aware of the buildpaths warnings with the latest master, and I'm addressing them with some upcoming package version bumps. Cheers, Bruce -- - Thou shalt not follow

Nothing in Xen respects --enable-sdl, and nothing in Xen links to libSDL, so this PACKAGECONFIG is obsolete. It looks like the last user of SDL in Xen was removed in "Remove internal tools/ioemu tree"

From: Andrei Gherzan <andrei.gherzan@...> Signed-off-by: Andrei Gherzan <andrei.gherzan@...> --- ...-Fix-buffer-overflow-on-workdir-path.patch | 32 ------------------- ...erlayfs_0.6.4.bb => fuse-over

To fix warnings when the buildpaths QA test is enabled, pass the file and debug prefix map options that were previously supplied only for reproducible builds, adding them to the DEBUG_PREFIX_MAP varia

From: Andrei Gherzan <andrei.gherzan@...> Signed-off-by: Andrei Gherzan <andrei.gherzan@...> --- ...-Fix-buffer-overflow-on-workdir-path.patch | 32 +++++++++++++++++++ .../fuse-overlayfs/fuse-overlayf

From: Andrei Gherzan <andrei.gherzan@...> This support is disabled by default and exposed via PACKAGECONFIG. Signed-off-by: Andrei Gherzan <andrei.gherzan@...> --- docs/00-INDEX | 3 +++ docs/podman.tx

From: Andrei Gherzan <andrei.gherzan@...> Podman can run in via a docker symlink emulating docker commands. By default this generates a runtime warning. This change silences it via the provided interf

From: Andrei Gherzan <andrei.gherzan@...> slirp4netns uses a TAP device to connect to the internet in an unprivileged way. Without the required kernel support (TAP/TUN), slirp4netns will fail at runti

Add an optional parameter that allows to override the stop signal that is used. Signed-off-by: Vasileios Anagnostopoulos <vasileios.anagnostopoulos@...> --- classes/image-oci-umoci.inc | 4 ++++ classe

From: Pascal Bach <pascal.bach@...> Signed-off-by: Pascal Bach <pascal.bach@...> --- classes/image-oci-umoci.inc | 34 +++++++++++++++++----------------- 1 file changed, 17 insertions(+), 17 deletions(

Perhaps someone here can help point me to relevant documentation. I'm wondering if there are some guidelines about which version(s) of docker/containerd/runc are compatible. I've searched through the

From: Andrei Gherzan <andrei.gherzan@...> Signed-off-by: Andrei Gherzan <andrei.gherzan@...> --- ...-Fix-buffer-overflow-on-workdir-path.patch | 32 +++++++++++++++++++ .../fuse-overlayfs/fuse-overlayf

From: Andrei Gherzan <andrei.gherzan@...> This support is disabled by default and exposed via PACKAGECONFIG. Signed-off-by: Andrei Gherzan <andrei.gherzan@...> --- docs/00-INDEX | 3 +++ docs/podman.tx

From: Andrei Gherzan <andrei.gherzan@...> Podman can run in via a docker symlink emulating docker commands. By default this generates a runtime warning. This change silences it via the provided interf

From: Andrei Gherzan <andrei.gherzan@...> slirp4netns uses a TAP device to connect to the internet in an unprivileged way. Without the required kernel support (TAP/TUN), slirp4netns will fail at runti

From: Andrei Gherzan <andrei.gherzan@...> Signed-off-by: Andrei Gherzan <andrei.gherzan@...> --- docs/00-INDEX | 3 +++ docs/podman.txt | 15 +++++++++++++++ docs/podman.txt.license | 3 +++ .../podman/p