Re: pseudo error building master with kas-container


Jan Kiszka
 

On 08.01.22 20:15, Trevor Woerner wrote:
On Sat 2022-01-08 @ 04:32:21 PM, Quentin Schulz wrote:
On January 8, 2022 3:13:17 AM GMT+01:00, Trevor Woerner <twoerner@...> wrote:
On Fri 2022-01-07 @ 11:21:38 PM, Quentin Schulz wrote:
On January 7, 2022 9:12:41 PM GMT+01:00, Trevor Woerner <twoerner@...> wrote:
In my experiments it seems like all I need is the update to kas-container to
add "--tmpfs /tmp" to KAS_RUNTIME_ARGS (around line 125). Are you going to
submit a patch to kas upstream?
Feel free to do it, I don't use kas-container, I use the kas container
from ghcr.io directly so this won't impact me and I wouldn't be able to
"maintain" this part and see if something breaks it. I anyway have as many
clues as you have on why this fixes pseudo issues so I wouldn't be able to
write a better commit log than you'd do.
Okay. Can I add your SOB line to the patch?
Thanks for asking. I wouldn't have minded were you to send this patch
without my SoB but if you want you can use foss+yocto@....

The important being that it's fixed ☺️
I wouldn't do something like that on purpose :-)
Let's see where this goes:
https://github.com/siemens/kas/pull/76/commits/eb8f5c90804dee5a1a649883e1d400d1058639b3
Could you send your patch to the kas mailing list for discussion? It
will probably just need a bit tuning on the reasoning:

Rootless podman uses fuse-overlayfs for the rootfs, and that seems to be
incomplete or otherwise incompatible with pseudo. When starting in
--isar mode, thus privileged, a real overlayfs is used, and that works.
And the build folder is not affected by this as it is mounted from the host.

Jan

--
Siemens AG, Technology
Competence Center Embedded Linux

Join yocto@lists.yoctoproject.org to automatically receive all group messages.