All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Trevor Woerner <twoerner@gmail.com>,
	Quentin Schulz <foss+yocto@0leil.net>
Cc: <yocto@lists.yoctoproject.org>, kas-devel <kas-devel@googlegroups.com>
Subject: Re: [yocto] pseudo error building master with kas-container
Date: Sun, 9 Jan 2022 12:16:44 +0100	[thread overview]
Message-ID: <b6e6216d-eebb-485a-35ba-e2e18f527721@siemens.com> (raw)
In-Reply-To: <20220108191515.GA21494@localhost>

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@gmail.com> 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@gmail.com> 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@0leil.net.
>>
>> 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


      parent reply	other threads:[~2022-01-09 11:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220104192528.GA25696@localhost>
2022-01-04 23:08 ` [yocto] pseudo error building master with kas-container Quentin Schulz
2022-01-06 13:50   ` Trevor Woerner
2022-01-06 14:28     ` Jan Kiszka
2022-01-06 19:28     ` Quentin Schulz
     [not found]       ` <20220107201240.GA13417@localhost>
2022-01-07 22:21         ` Quentin Schulz
2022-01-08  2:13           ` Trevor Woerner
2022-01-08 15:32             ` Quentin Schulz
     [not found]               ` <20220108191515.GA21494@localhost>
2022-01-09 11:16                 ` Jan Kiszka [this message]

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=b6e6216d-eebb-485a-35ba-e2e18f527721@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=foss+yocto@0leil.net \
    --cc=kas-devel@googlegroups.com \
    --cc=twoerner@gmail.com \
    --cc=yocto@lists.yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.