Raspberry Pi build action

[TiemenSch]

Would it be possible to create an image variant of uCore tailored to be directly installed on Raspberry Pi's? I would be very much insterested to change my Raspberry Pi setups to work with containerized deployment, but first time setup of anything custom-Fedora on a Pi is quite elaborate (See https://medium.com/geekculture/how-to-install-fedora-on-a-headless-raspberry-pi-62adfb7efc5)

A lot of these steps seem to be fit for automation and perhaps not even necessary when basing off uCore, but the dream would be:

• Burn uCore image to SD
• Paste SSH key in correct folder on SD
• Boot and wait
• SSH into Pi with said key as authentication
• (Optional): Rebase on custom image.

Would such a setup be interesting to support?

[surdy]

I am starting to move severs in my homelab to ucore so I started thinking about possibility of also moving my raspberry pi's to ucore. That is how I landed here.

I'm still a noob to ublue world. So I might be wrong on a few of these things. Here is why I think deploying ucore on Raspberry pi might not be that straight forward

1. There is no aarch64 support for ucore yet (Add aarch64 support #15) . This is important but should be straight forward in terms of just dedicating time and effort to set up an automation.

2. There is no ucore image to burn SD card in the traditional raspberry pi sense. Images (overloaded term) in the ublue world is an OCI image not an SD card/ISO image. While desktop based ublue flavors have moved to ISO based distribution, ucore remains with the "rebase" style deployment model as it is based on Fedora Core OS (FCOS) and not Silverblue. https://universal-blue.discourse.group/t/is-there-a-reason-ucore-hasnt-adopted-the-ujust-alias-or-isos/4668. I don't think there is any short term plan to change this. Atleast I could not find one as an outsider. Regardless deployment mechanism is secondary to my next point.

3. The article you liked talks about deploying standard fedora onto a raspberry pi. Which is quite different and IMO much more straightforward than deploying FCOS on raspberry pi. https://docs.fedoraproject.org/en-US/fedora-coreos/provisioning-raspberry-pi4/. Again, not impossible to solve for this but something that needs to be figured out for a "batteries included" approach before we can even attempt to get to the rebase step of my point above.

Maybe the answer is coming up with a custom approach for raspberry pi based deployments. But before we get there we need to start building aarch64 images.

Happy to collaborate on this if any help is required.

[heaviss]

Any updates here since aarch64 support was released?

[shvetsnikita]

Would it be possible to create an image variant of uCore tailored to be directly installed on Raspberry Pi's?

Is there a possibility that solving it the other way around (by adjusting RPi to be usable with uCore) might be a more appropriate solution? In that case, installation could be performed in two steps:

1. The user makes their board ARM SBBR-compliant by flashing one of the following firmware (in the same sense as coreboot is firmware)
   https://github.com/pftf/RPi4/
   https://github.com/worproject/rpi5-uefi
   https://github.com/ansleythompson/blueberry
   https://github.com/edk2-porting/edk2-rk3588
   https://sd-card-images.johang.se/boards.html (only boot image)
2. Then, the user deploys uCore or Bluefin using the same approach they would use on x86 hardware.

By directing users to step one, uCore and Bluefin gain support for around 80 boards instead of 2, so this may be the right thing to do?

[TiemenSch]

Rather interesting approach! I might try this at some point with a spare RPi4 I have lying around somewhere. Very eager to see how stable this would run.