[Feature]: Support for third-party / community OS images

[naltatis]

Prerequisites

• I have searched the existing issues and this feature has not been requested before

Feature Area

Custom image handling

Problem Statement

We build Armbian-based images for evcc (open source solar charging and energy management) for boards like NanoPi R3S, R76S and Zero2. Our images use the Armbian build framework but do a lot of customization on top (cockpit, caddy, wifi setup, etc), so a simple extension in armbian/os is not a good fit.

Right now there is no way for projects like ours to make their images discoverable in the Armbian Imager. There is a "Use Custom Image" button but it's quite hidden and requires users to download images manually first.

We already have our images listed in Raspberry Pi Imager using a hosted JSON file with image metadata: https://github.com/evcc-io/images/blob/main/rpi-imager.json

Proposed Solution

Support external image sources in the Armbian Imager. Projects building on Armbian could host a JSON file with image metadata (download URL, SHA256, size, board list) and have their images show up in the Apps tab or a new "Community" section.

Another option would be to support customized / branded versions of Armbian Imager. Have you thought about this use-case already or have plans for it?

Alternatives Considered

• Armbian extension in armbian/os: Our customization is too complex (multiple 3rd party repos, custom services) and we'd lose control over our release cycle.
• "Use Custom Image" button: Works but requires manual download and is easy to miss.

How important is this feature to you?

Would significantly improve my workflow

Use Case

Our installation instructions currently tell users to manually download images and flash with Balena Etcher or RPi Imager: https://docs.evcc.io/en/docs/installation/linux-image

Being listed in the Armbian Imager would make the process much simpler for users on NanoPi and other Armbian-supported boards.

Mockups / Examples

No response

Additional Context

Our image builds: https://github.com/evcc-io/images

Happy to help if there's interest.

[SuperKali]

@naltatis We'll discuss this internally and let you know.

[igorpecovnik]

We are supporting the idea and similar question came up some time ago by @adeepn before we developed this tool - for website. Web download is about to become fully synchronized soon (not yet at this point) and what will be in the imager will also be on the website on the same way.

Before jumping on a code, lets figure out what would be the minimal dataset required for JSON exchange. There are two ways to deal with this - one is to load 3rd party JSON file(s) directly (not want this) or pull them when we are generating ours https://github.armbian.com/armbian-images.json I think this last option is better as we have opportunity to double check / verify if links are (still) alive and not provide dead links (even from 3rd party) via our web site / imager.

Also we need to make this as universal as possible in order to be able to provide as unusual images as possible.

[adeepn]

We are supporting the idea and similar question came up some time ago by @adeepn before we developed this tool - for website.

I think the question here is a bit broader. I was originally trying to discuss building our own images for the boards we support (although with the introduction of extensions this now seems less necessary, except perhaps to slightly offload the Armbian infrastructure).

This proposal aligns with the idea of supporting additional images with custom software inside the Imager (regardless of whether they are hosted on Armbian servers or elsewhere). Maybe it makes sense to discuss how far Armbian is willing to go in supporting the build and distribution of additional images for third-party groups under a separate set of rules?

Alternatively, we could define general rules for adding third-party system images into the Imager (which would also include validation and availability checks).

[igorpecovnik]

supporting additional images with custom software inside the Imager (regardless of whether they are hosted on Armbian servers or elsewhere

I am open for this.

how far Armbian is willing to go

I only want to keep control to verify if images that comes via JSON really exists. If 3rd party infra is offline, images are auto-removed and re-added once they are back online.

we could define general rules

That we need to do before coding and testing.