Include the xt-statistic kernel module required by K3S for iptables configuration. Signed-off-by: Kamil Dziezyk <kamil.dziezyk@...> Change-Id: I7592261c65c7c0831ce553ee907fba9e3e458b6f ---

Update k3s.service with the latest changes from install.sh script. Add k3s-killall.sh script to stop all of the K3s containers and reset the containerd state. The killall script cleans up containers,

Indeed. I'll take care of the changes, since I can run tests as I go. What branches are you using ? I can backport to wherever it makes sense. Bruce -- - Thou shalt not follow the NULL pointer,

Hi Bruce, This is the current fix that I have for docker-moby and cni recipes and I think it is aligned with the patch that you linked since you are also setting the SRCREV_FORMAT: ``` diff --git

It is only required by master that the oe-core commit only exists in oe-core master and next release(kirkstone) branches: $ git br -r --contains 8e26252b45   origin/HEAD -> origin/master  

v2 is staged on master-next. If this is needed anywhere else than master (i.e. honister), let me know ... It wouldn't break anything on honister, but I'm trying to keep the changes there to a

From: Kai Kang <kai.kang@...> According to oe-core commit 8e26252b45 layer.conf: Extend recipes not to install without explict dependencies pkgconfig-native is not deployed in sysroot by

My fault. I referred to wrong commit. Thank you for pointing out. Regards, Kai -- Kai KangWind River Linux

Sorry, just ref the commit in Yocto. Will ref to URL link next time. Regards, Kai -- Kai KangWind River Linux

I've actually been going through and fixing these as they pop up, and just had to do it for

Hi, Recently I realized that we are having issues with setscene tasks (for docker-moby and cni recipes) where the packages were rebuild even already have their tasks in the sstate mirror and

Ah yes, they've committed crimes in autogen.sh, that I hadn't noticed creeping in. I've bumped crun to the latest, and will confirm no network access before pushing. Bruce -- - Thou shalt not

Bruce, Thank you for the response. I believe I am running into the same issue attempting to build podman with crun as the container runtime. These are the steps I have taken to reproduce the error:

I was just finishing up a move to the master branch of the repository .. because it now seems that they are willing to force-push crui-dev. At the same time, I'm moving it to 3.16.1. But thanks for

Commit e49ce513c8df43e8d3b30b7acfbe7bd496d89862 is no longer in repo. Use 95ead14874244f3c12e5970a74d1f4dd2433d652 instead, which is tagged 3.14. Signed-off-by: Chen Qi <Qi.Chen@...> ---

ipv6 is always in my distro features, so I didn't notice that myself. I've added ipv6 to the required distros check of podman, so it will be caught in the future. Bruce -- - Thou shalt not follow

There's definitely something different in your image composition than the core-image* (poky based) that are used in much of the (my) regular testing. In a systemd based image, you shouldn't need to

I had to add a /etc/containers/libpod.conf file with the following content: cgroup_manager = "cgroupfs" runtime = "/usr/bin/crun" And now podman can run: @iotgate:~# podman run

After passing 'ipv6' into DISTRO_FEATURES, ip6tables gets installed. ~# podman run hello-world .... [ 207.201607] cni-podman0: port 1(veth6b661354) entered disabled state Error: systemd cgroup flag

I think you should refer to this oe-core commit instead: https://git.openembedded.org/openembedded-core/commit/?id=8e26252b45b7660c7c67c702411bdec187a76ffc