Self-build minimal image for RockPI-S too big

[dg4gg8cb9s]

Hi,

trying to get a bit deeper into Armbian, I tried to create my own minimal Trixie-based image for the RockPI-S. I'm using a Ubuntu Noble VM and I managed to run a successfull build following the quick start guide.

However, creating an image using

./compile.sh build BOARD=rockpi-s BRANCH=current BUILD_MINIMAL=yes KERNEL_CONFIGURE=no RELEASE=trixie 

leads to an image with a size around 1.5GB. Compared to the downloadable minimal images, which have 200MB-300MB, this is quite large.

 

Does anyone has any hints on how to proceed in order to self-build images comparable to the ones offered for download?

 

Cheers,

[brentr]

The uncompressed minimal image is about 1.5GB.

 

How large is your trixie based image after you compress it with xz ?

 

[laibsch]

2 hours ago, dg4gg8cb9s said:

However, creating an image using

./compile.sh build BOARD=rockpi-s BRANCH=current BUILD_MINIMAL=yes KERNEL_CONFIGURE=no RELEASE=trixie 

leads to an image with a size around 1.5GB. Compared to the downloadable minimal images, which have 200MB-300MB, this is quite large.

 

 

adding COMPRESS_OUTPUTIMAGE to your call will compress your image.

 

$ ./compile.sh build BOARD=rockpi-s BRANCH=current BUILD_MINIMAL=yes KERNEL_CONFIGURE=no RELEASE=trixie COMPRESS_OUTPUTIMAGE=xz
[...]
$ ls -lh output/images/*.xz
-rw-rw-r-- 1 user root 342M Aug 15 01:03 output/images/Armbian-unofficial_25.11.0-trunk_Rockpi-s_trixie_current_6.12.41_minimal.img.xz

 

[dg4gg8cb9s]

Hi,

 

many thanks for your hints @brentr and @laibsch! 😀

 

Using 

COMPRESS_OUTPUTIMAGE=xz

did the trick and the image size is now more in an expected range.

 

However, using the paramters and commandline above gives me an image with a size of 342MB whereas the current rolling Trixie image is 273MB.

I don't think it is a big deal, but I still would like to understand the difference 😊

 

Cheers

[laibsch]

dig through the github actions, how the images are compiled is public information ;-)