In RPI Imager v2.x the option to customize local images has been removed. In order to have image customization you need to have your own "Content Repository".
Starting with version RPI Imager v2.0.2 the files in this repository can be paths to your local files or URLs to locally hosted files.
local_repo.json illustrates such a minimal configuration for locally hosted files and locally stored files.
If you want to locally host your files, you can do so via python 3 one liner. In the directory where your images are, run:
# Start webserver on port 3333
python3.11 -m http.server 3333To use this local repo go to "App Options" -> "Content Repository" -> "Use custom file". You will need to re-select this file every time you restart the Imager (due to security concerns).
Newer version of Pi OS use cloudinit-rpi instead of systemd for customization, so your entry has to reflect that OR your custom image does not use cloud-init - aka you remove it during your image adaptation.
I highly recommend you to switch to cloudinit-rpi though, it provides a lot of quality of life improvements, but in a pinch you can still use the systemd format.
@tdewey-rpi Interesting - I have a custom image based on "Pi OS Lite Trixie (2025-10-01)" and with that, customization works fine. I have not tried with the latest December release though - do you by any chance know the cutoff date at which
cloudinit-rpiis mandatory?Edit: https://www.raspberrypi.com/news/cloud-init-on-raspberry-pi-os/ It seems that this happened some time in November...