Avi Deitcher

> but without platforms flag we will build all platforms in all tasks/runners and it looks like a waste of time/space You are correct, I wasn't very clear. We always...

OK, I stand corrected. linuxkit _used_ to check the registry for all arch-specific tags and then update the multi-arch index. And it still does. That chunk never was removed. I...

With `lkt pkg manifest`, we can avoid the issue by having that run after everything else is complete. Our steps then are: 1. Wait for the `pkg manifest` and `pkg...

@giggsoff with all of that work done on linuxkit, it is about time to get this moving forward. I have one open PR on linuxkit, it will merge in early...

> Is it what you need (subset of packages for riscv64 as well as for amd64 and arm64)? > Other packages compiled only for amd64, arm64, not for riscv64. Yeah,...

> any idea why the build is failing? No, but I haven't dug deeply enough yet @eriknordmark . It doesn't matter, though, as we still have some changes to make,...

> any idea why the build is failing? @eriknordmark yes, I do now. It is the very "build dependency" problem that delayed us from moving to this version of linuxkit...

No, that is not it, and I am quite confused. Maybe @giggsoff knows? Here is the beginning of `pkg/pillar/Dockerfile`: ```dockerfile FROM lfedge/eve-dom0-ztools:ff71338c79558620a3d6dd770ad0291b786e759d as zfs ``` But that tag `ff71338c79558620a3d6dd770ad0291b786e759d` does...

Haha, crossed wires! Thanks @giggsoff . So I will hold until you have that one fixed.

Once that is in, I will rebase and push out. That should trigger the few failing points in CI due to the chained builds, which I will fix.