You can increase the size of the rootfs partition in make menuconfig under Target images -->, near the bottom. I don't know if this applies to your target, but on some (x86 for one) if you make it too big, image creation will take forever (this is why it's artificially limited to 1GB by the ASU server). In any case, 1-2 GB rootfs size is way overkill for any application on OpenWrt.
EDIT: Which sysupgrade client are you using? owut is the only one that lets you resize the root partition...
I attempt this process in Luci by installing and using luci-app-attendedsysupgrade.
LuCi: System -> Attended Sysupgrade -> Search for firmware upgrade
I selected the desired version from the dropdown, and clicked Request Sysupgrade
Then I waited until the server builds the custom image that includes all the packages that are currently installed. But the build process terminates with the "out-of-space" message.
owut (new upgrade client which replaces attendedsysupgrade in 24.10) can handle this with the --rootfs-size parameter (up to 1 GB). auc does not have an option for non-default filesystem size. Remove some of the large packages so the build will fit in the default size. Then after 24.10 is installed increase the size and install the packages.
To have GBs of space for stuff other than packages, create a separate data partition and keep the rootfs under 1 GB. Upgrading will preserve the partition.
Thank you very much, that worked. I uninstalled Docker and deleted the Docker image, then the image could be downloaded. After installing the 24.10 image, however, a new problem occurred. The interface to the LAN no longer transmitted any data (the LED no longer flashed), but the interface to the WAN worked. I have restored a backup and now running version 23.05.
I have made the following changes to the standard configuration of OpenWRT:
use of AdguardHome as DNS filter (uses port 53, dnsmasq uses port 5353 and is configured as upstream DNS in AdguardHome)
use of openssh instead of dropbear
What could be the reason for the malfunction of version 24.10?
Maybe some incompatibility in the /etc/config/network settings? If you bring the device up on 24.10 and hack around on the br-lan device or lan interface, you can probably figure it out.