Re: [RFC cip-dev][isar-cip-core][PATCH 0/4] switch to rootless build
Jan Kiszka <[email protected]> Mon, 27 Jul 2026 12:13:41 +0200
| Newsgroups | org.cip-project.lists.cip-dev |
|---|---|
| Message-ID | <[email protected]> |
On 27.07.26 10:06, Quirin Gylstorff wrote: > > > On 7/27/26 8:13 AM, Jan Kiszka wrote: >> On 24.07.26 12:51, Quirin Gylstorff wrote: >>> From: Quirin Gylstorff <[email protected]> >>> >>> This patchset contains the necessary changes to switch >>> isar-cip-core to the new rootless build. >>> >>> This has an impact on downstream as the classes need the new >>> rootless changes. So this is no longer compatible with isar before >>> the rootless merge. >> >> But this remains opt-in for downstream, except for updating Isar to a >> compatible revision. That alone is not new to isar-cip-core. However, >> this change also demands kas to be very recent. That is a not so often >> the case. But we need to do this step at some point, and we are still >> early enough in the release of the next version to move forward, I would >> say. >> >>> >>> The patchset is build with the following pipeline >>> https://gitlab.com/cip-project/cip-core/isar-cip-core/-/ >>> pipelines/2702946001 >> >> And that means our cluster is recent enough to host this. Downstream may >> not yet, maybe worth to point out in the README.md as well (if Isar has >> some info on that, just link there). > > I have not seen anything in Isar. Has it even an impact on existing > builds with priviledged containers? That should remain unaffected. My point is the requirements host-side for doing rootless builds: We need a recent kernel, and that is only revealed during the build, indirectly. Jan -- Siemens AG, Foundational Technologies Linux Expert Center