public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: Michael Adler <michael.adler@siemens.com>
To: cip-dev@lists.cip-project.org
Cc: Michael Adler <michael.adler@siemens.com>
Subject: [PATCH 0/1] linux-cip: add kernel config snippet for container compatibility
Date: Wed,  8 Jan 2025 11:07:54 +0100	[thread overview]
Message-ID: <20250108100755.55673-1-michael.adler@siemens.com> (raw)

While the cip-core x86-64 kernel configuration includes the necessary options
for container engines like Docker, the arm64 configuration does not.
I have identified the required kernel configuration options to ensure
compatibility with Docker and Podman.
Instead of integrating these options directly into the arm64 configuration, I
am providing them as a drop-in snippet to support custom kernel
configurations.

Note: I am open to feedback on whether this should remain a drop-in snippet or
be merged into the default configuration.


Michael Adler (1):
  linux-cip: add kernel config snippet for container compatibility

 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

-- 
2.47.1



             reply	other threads:[~2025-01-08 10:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-08 10:07 Michael Adler [this message]
2025-01-08 10:07 ` [PATCH 1/1] linux-cip: add kernel config snippet for container compatibility Michael Adler
2025-01-09  8:11   ` [cip-dev] " Florian Bezdeka
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=20250108100755.55673-1-michael.adler@siemens.com \
    --to=michael.adler@siemens.com \
    --cc=cip-dev@lists.cip-project.org \
    /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