Docker firmware selector rootfs size

Hello,

I have a question about the firmware selector, I need to create a build for x86 with docker packages (docker docker-compose dockerd luci-app-dockerman luci-lib-docker)

Unfortunately when I go to create the build it reports the error out of space...

Is there a way to generate the build larger than allowed? Unfortunately the docker packages are large...

Ignoring, exclude it (-e/-ef) to override.
error: ext4_allocate_best_fit_partial: failed to allocate 4565 blocks, out of space?
make[3]: *** [/builder/include/image.mk:399: /builder/build_dir/target-i386_pentium4_musl/linux-x86_generic/root.ext4] Error 1
make[2]: *** [Makefile:268: build_image] Error 2
make[1]: *** [Makefile:163: _call_image] Error 2
make: *** [Makefile:337: image] Error 2

1 Like

You can mount separate partition on the 2nd half of the disk.
squashfs is more reliable and "router-like" as you can fsck overlay and revert to factory files if you need.

1 Like

thanks for the great replay!

I thought maintenance was more... "fast".
It would be nice to have a subscription for "stable updates" without having to manually create a build every time.

For 24.10 and later, Firmware Selector is the only ASU client that does not support resizing the rootfs partition. If you can use on-device clients for your upgrades (LuCI Attended Sysupgrade or owut), then they can be used to perform the ASU builds and include a non-default value for the rootfs partition size (up to 1024MB when using the OpenWrt ASU server).

1 Like

Thanks a lot! I will try with LuCI Attended Sysupgrade and understand how to maintain the current disk size... do you already have some reference?

Assuming your version of LuCI Attended Sysupgrade is new enough, then use https://openwrt.org/docs/guide-user/installation/sysupgrade.owut#expanding_root_file_system LuCI now looks for the owut setting and uses that.

1 Like

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.