From: Florian Bezdeka <florian.bezdeka@siemens.com>
To: cip-dev@lists.cip-project.org
Cc: Michael Adler <michael.adler@siemens.com>
Subject: Re: [cip-dev] [PATCH 1/1] linux-cip: add kernel config snippet for container compatibility
Date: Thu, 09 Jan 2025 09:11:31 +0100 [thread overview]
Message-ID: <ae76220a96b4e1a58889755492db2079cd251cc0.camel@siemens.com> (raw)
In-Reply-To: <20250108100755.55673-2-michael.adler@siemens.com>
On Wed, 2025-01-08 at 11:07 +0100, Michael Adler via lists.cip-
project.org wrote:
> Obtaining a fully functional kernel configuration as required by popular
> container engines such as Docker or Podman can be challenging. By
> setting the Bitbake variable USE_CIP_KERNEL_CONTAINER_CONFIG to 1, a
> kernel config snippet is included to ensure compatibility with these
> container engines.
>
> Note: This feature is designed to be separate from the cip-kernel-config
> project to allow for custom kernel configurations.
>
> Signed-off-by: Michael Adler <michael.adler@siemens.com>
> ---
> conf/machine/qemu-amd64.conf | 1 +
> conf/machine/qemu-arm64.conf | 1 +
> recipes-kernel/linux/files/container.cfg | 114 ++++++++++++++++++++++
> recipes-kernel/linux/linux-cip-common.inc | 5 +
> 4 files changed, 121 insertions(+)
> create mode 100644 recipes-kernel/linux/files/container.cfg
>
> diff --git a/conf/machine/qemu-amd64.conf b/conf/machine/qemu-amd64.conf
> index d786646..dad6504 100644
> --- a/conf/machine/qemu-amd64.conf
> +++ b/conf/machine/qemu-amd64.conf
> @@ -10,4 +10,5 @@ DISTRO_ARCH = "amd64"
>
> IMAGE_FSTYPES ?= "ext4"
> USE_CIP_KERNEL_CONFIG = "1"
> +USE_CIP_KERNEL_CONTAINER_CONFIG = "1"
> KERNEL_DEFCONFIG = "cip-kernel-config/${KERNEL_DEFCONFIG_VERSION}/x86/cip_merged_defconfig"
> diff --git a/conf/machine/qemu-arm64.conf b/conf/machine/qemu-arm64.conf
> index a2c5e53..8fd824c 100644
> --- a/conf/machine/qemu-arm64.conf
> +++ b/conf/machine/qemu-arm64.conf
> @@ -10,6 +10,7 @@ DISTRO_ARCH = "arm64"
>
> IMAGE_FSTYPES ?= "ext4"
> USE_CIP_KERNEL_CONFIG = "1"
> +USE_CIP_KERNEL_CONTAINER_CONFIG = "1"
I get the idea, but the user / downstream could append your kconfig
file to the SRC_URI directly. No need for the variable. Files ending in
.cfg are "auto detected" as kernel configuration files.
> KERNEL_DEFCONFIG ?= "cip-kernel-config/${KERNEL_DEFCONFIG_VERSION}/arm64/cip_merged_defconfig"
>
> # watchdog is not yet supported in our QEMU executor for this platform, disable it
> diff --git a/recipes-kernel/linux/files/container.cfg b/recipes-kernel/linux/files/container.cfg
> new file mode 100644
> index 0000000..18f8b2b
> --- /dev/null
> +++ b/recipes-kernel/linux/files/container.cfg
> @@ -0,0 +1,114 @@
> +# Copyright (c) Siemens AG, 2025
> +#
> +# Authors:
> +# Michael Adler <michael.adler@siemens.com>
> +#
> +# SPDX-License-Identifier: MIT
> +
> +# Kernel configuration required by container runtimes such as Docker.
> +# Based on the following scripts:
> +#
> +# - https://github.com/moby/moby/blob/master/contrib/check-config.sh
> +# - https://github.com/opencontainers/runc/blob/main/script/check-config.sh
> +#
> +# NOTE: CONFIG_SECURITY_SELINUX and CONFIG_SECURITY_APPARMOR are intentionally
> +# not enabled.
> +
> +CONFIG_NAMESPACES=y
> +CONFIG_NET_NS=y
> +CONFIG_PID_NS=y
> +CONFIG_IPC_NS=y
> +CONFIG_UTS_NS=y
> +
> +CONFIG_CPUSETS=y
> +CONFIG_CRYPTO=y
> +CONFIG_CRYPTO_AEAD=y
> +CONFIG_CRYPTO_GCM=y
> +CONFIG_CRYPTO_GHASH=y
> +CONFIG_CRYPTO_SEQIV=y
> +CONFIG_KEYS=y
> +CONFIG_MEMCG=y
> +CONFIG_CHECKPOINT_RESTORE=y
> +
> +CONFIG_OVERLAY_FS=m
> +
> +CONFIG_CGROUPS=y
> +CONFIG_CGROUP_CPUACCT=y
> +CONFIG_CGROUP_DEVICE=y
> +CONFIG_CGROUP_FREEZER=y
> +CONFIG_CGROUP_NET_PRIO=y
> +CONFIG_CGROUP_PERF=y
> +CONFIG_CGROUP_PIDS=y
> +CONFIG_CGROUP_SCHED=y
> +CONFIG_FAIR_GROUP_SCHED=y
> +CONFIG_CGROUP_BPF=y
> +CONFIG_BPF_SYSCALL=y
> +CONFIG_CFS_BANDWIDTH=y
> +CONFIG_RT_GROUP_SCHED=y
> +
> +CONFIG_HUGETLBFS=y
> +CONFIG_CGROUP_HUGETLB=y
> +
> +CONFIG_BLK_CGROUP=y
> +CONFIG_BLK_CGROUP_IOCOST=y
> +CONFIG_BLK_DEV_THROTTLING=y
> +
> +CONFIG_NET=y
> +CONFIG_NET_CLS_CGROUP=y
> +CONFIG_NET_CLS_ACT=y
> +CONFIG_NET_EMATCH=y
> +CONFIG_NET_SCHED=y
> +CONFIG_NETLABEL=y
> +CONFIG_INET=y
> +CONFIG_POSIX_MQUEUE=y
> +
> +CONFIG_NETDEVICES=y
> +CONFIG_NET_CORE=y
> +CONFIG_VETH=m
> +CONFIG_BRIDGE=m
> +CONFIG_BRIDGE_NETFILTER=m
> +CONFIG_BRIDGE_VLAN_FILTERING=m
> +CONFIG_VXLAN=m
> +CONFIG_IPVLAN=m
> +CONFIG_MACVLAN=m
> +
> +CONFIG_NETFILTER=y
> +CONFIG_NETFILTER_ADVANCED=y
> +CONFIG_NETFILTER_XT_MARK=m
> +CONFIG_NETFILTER_XT_MATCH_ADDRTYPE=m
> +CONFIG_NETFILTER_XT_MATCH_BPF=m
> +CONFIG_NETFILTER_XT_MATCH_COMMENT=m
> +CONFIG_NETFILTER_XT_MATCH_CONNTRACK=m
> +CONFIG_NETFILTER_XT_MATCH_IPVS=m
> +CONFIG_IP_NF_FILTER=m
> +CONFIG_IP_NF_IPTABLES=m
> +CONFIG_IP_NF_MANGLE=m
> +CONFIG_IP_NF_NAT=m
> +CONFIG_IP_NF_TARGET_MASQUERADE=m
> +CONFIG_IP_NF_TARGET_REDIRECT=m
> +CONFIG_IP_VS=m
> +CONFIG_IP_VS_NFCT=y
> +CONFIG_IP_VS_PROTO_TCP=y
> +CONFIG_IP_VS_PROTO_UDP=y
> +CONFIG_IP_VS_RR=m
> +
> +CONFIG_NF_TABLES=m
> +CONFIG_NF_TABLES_INET=y
> +CONFIG_NF_TABLES_NETDEV=y
> +CONFIG_NF_CONNTRACK=m
> +CONFIG_NF_CONNTRACK_FTP=m
> +CONFIG_NF_CT_NETLINK=m
> +CONFIG_NF_NAT=m
> +CONFIG_NF_NAT_IPV4=m
> +CONFIG_NF_NAT_MASQUERADE=m
> +CONFIG_NF_NAT_NEEDED=m
> +
> +CONFIG_NFT_COMPAT=m
> +CONFIG_NFT_CT=m
> +CONFIG_NFT_HASH=m
> +CONFIG_NFT_LIMIT=m
> +CONFIG_NFT_LOG=m
> +CONFIG_NFT_MASQ=m
> +CONFIG_NFT_NAT=m
> +CONFIG_NFT_REDIR=m
> +CONFIG_NFT_REJECT=m
All CIP kernels are building fine with this config enabled? I'm missing
the testing part...
> diff --git a/recipes-kernel/linux/linux-cip-common.inc b/recipes-kernel/linux/linux-cip-common.inc
> index 5d1b8ac..437ee17 100644
> --- a/recipes-kernel/linux/linux-cip-common.inc
> +++ b/recipes-kernel/linux/linux-cip-common.inc
> @@ -23,4 +23,9 @@ SRC_URI += " \
> https://cdn.kernel.org/pub/linux/kernel/projects/cip/${KERNEL_MAJOR_MINOR}/linux-cip-${PV}.tar.xz \
> "
>
> +SRC_URI:append = " ${@ \
> + 'file://container.cfg' \
> + if d.getVar('USE_CIP_KERNEL_CONTAINER_CONFIG') == '1' else '' \
> + }"
> +
As said, could be moved to the user.
> S = "${WORKDIR}/linux-cip-${PV}"
> --
> 2.47.1
next prev parent reply other threads:[~2025-01-09 8:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 10:07 [PATCH 0/1] linux-cip: add kernel config snippet for container compatibility Michael Adler
2025-01-08 10:07 ` [PATCH 1/1] " Michael Adler
2025-01-09 8:11 ` Florian Bezdeka [this message]
2025-01-08 10:17 ` [PATCH 0/1] " MOESSBAUER, Felix
2025-01-09 7:58 ` Jan Kiszka
2025-01-24 6:07 ` nobuhiro1.iwamatsu
2025-01-28 9:43 ` Michael Adler
2025-01-30 21:57 ` nobuhiro1.iwamatsu
2025-02-03 16:35 ` Michael Adler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ae76220a96b4e1a58889755492db2079cd251cc0.camel@siemens.com \
--to=florian.bezdeka@siemens.com \
--cc=cip-dev@lists.cip-project.org \
--cc=michael.adler@siemens.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox