Failing because of

error:
input:
container.from resolve:
failed to resolve image ghcr.io/9elements/firmware-action/coreboot_4.19:main:
failed to resolve source metadata for ghcr.io/9elements/firmware-action/coreboot_4.19:main:
failed to copy:
httpReadSeeker:
failed open:
content at https://ghcr.io/v2/9elements/firmware-action/coreboot_4.19/manifests/sha256:b0beef78d1d9a2398e5909c6ccb92416eccb1aa7fc33e60ea442493b0de14d00 not found:
not found

Now when I am thinking about this, it is inconvenient that stuff like source or exported variable will not work across elements in the slice. Maybe on each step we could export the env and the import it before the next command?

I don't know ... not sure if this is a good idea anymore.

So the removed DefconfigPath for EDK2 is now part of the BuildCommand field or how does that work in practice?

I did not know in which order the PR's will get merged ;)

Oh sorry, I misread the comment. Yes, the general idea is to not use the DefconfigPath for edk2. It was Patrick's idea if I am not mistaken. It is to store build flags and arguments for edk2 build. Very hacky non-standard solution.

I believe that it was meant to simplify local builds.

If we would switch to BuildCommand as slice, then the whole JSON config would be more readable and then I would not see any good reason for this DefconfigPath.

However the issue is that exported variables or sourceed files will not work across elements in the slice. But having the commands separately would be much nicer for debugging with interactive dagger debug, I think.