Hey Quentin,

Wow not bad, I'm batting 0/2 so far… lol!

On Thu 2022-01-06 @ 08:28:36 PM, Quentin Schulz wrote:

On January 6, 2022 2:50:47 PM GMT+01:00, Trevor Woerner <twoerner@...> wrote:

On Wed 2022-01-05 @ 12:08:15 AM, Quentin Schulz wrote:

I've had similar issues recently with kas-container and podman. What was
required were two things:
- passing --tmpfs /tmp to podman run,

I don't think --tmpfs is an option, but I modified my kas-container script to
add a "--tmpdir /tmp" option (and verified it with ps while running)

https://docs.podman.io/en/latest/markdown/podman-run.1.html#tmpfs-fs

Curious. When I run "podman -h" on the cmdline it only shows a --tmpdir option

$ podman -h | grep tmp
--tmpdir string Path to the tmp directory for libpod state content.
Note: use the environment variable 'TMPDIR' to change the temporary storage location for container images, '/var/tmp'.

I wasn't talking about uids or gids, but pids_limit in containers.conf for podman on your host. See:
https://man.archlinux.org/man/containers.conf.5.en

We discovered that it just had nothing to do with Bitbake/pseudo or
whatever, because with a fork bomb we reached the max of 2048 processes
(within the container) before the container started to fail us.

Without those two changes, I've never been able to successfully build even
core-image-minimal for qemu-x86_64.

Very nice, thanks for the info :-)

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?