Dimitris Karakasilis

I used the contents of this zip file: https://github.com/pftf/RPi4/releases/tag/v1.35 as my `--efi-dir` and I built an image with this command: ``` docker run -v $PWD:/work -v /var/run/docker.sock:/var/run/docker.sock --privileged -i --rm...

I tried the same command (see above) with this image: `quay.io/kairos/opensuse:leap-15.5-standard-arm64-rpi4-v2.4.3-k3sv1.27.6-k3s1` and it still works with no errors. Our differences are: - the contents of the `--efi-dir` (to be honest,...

Looking again, I see you had the `fdisk -l` problem also with the released image. Then the problem must be on the external disk somehow, because the rest of the...

I've ordered an nvme disk and a USB enclosure, it should be here next week. Unless someone else beats me to it, I will try again as soon as its...

Let's consider creating a luet package with these files and use it in every flavor (they should work on any flavor). We might also need the arm versions of those...

We need to implement a test to make sure we don't break it again in the future.

I think `peg` allows us to use different user and password to ssh to the VM. The question is where do we find the non-Kairos ISO. I had a similar...

Why not use a directory dedicated to actual cloud-configs like the description suggests? Then there is no reason to skip logs, since any file that is skipped in a directory...

The only problem is that sometimes people forget to put the header at the top of the file or things like that and the file they expected to be run...

This is a good middle ground. I would still prefer to avoid parsing a thousand different files to discover only those that look like cloud config files. But given the...