I have seen SO MANY threads complaining about this and IDK how it ever got posted the way it is… The stock Beagel Bone Black has a 3.6gb eMMC. ALL of the builds that SHOULD fit on it leave ZERO space for anything. You can’t expand the file system theres no space. you can’t even save a text file. zero space. its like a read only system but worse and its so frustrating. If you software images don’t fit on your device AND THEY DON"T Then don’t post them as eMMC images!? Its bad enough that the download server drop connection like 19 times in 20 and I have to restart but MAN! This is rock bottom kinds of bad. The very least you could do is lable them so some poor shmuck like me doesn’t waste there money and time trying to go SD Free when I could have used a Pi that works jsut fine and is faster and cheaper.
And a very warm welcome to you too! 
Clearly, we’re not reading the same forum and I had to turn my BBGW on to check,
but that is filled 60%. Granted, it’s not the latest and greatest, but I personally have
yet to be in your situation (or any of the thousands you claim to represent).
I also don’t download a new image every day (it isn’t required, once you have a stable)
and I am sorry that you seem to live in a place with Internet so unreliable,
but that can hardly be blamed on beagleboard.org now, can it? Well, clearly, but hardly deserved.
True, Pi’s have their uses; rather nifty devices, but SD free, they’re not.
Ok, not entirely true: My Pi5 has an NVMe disk and I’m very happy with it.
Yeah, sadly the xfce/lxqt images take everything… The IoT image is a better starting point… As far as why the xfce image is still available as a flasher, when it was removed users would still complain about the lack of it… So it’s there, 100% eMMC utilization…
Which download/file is failing for you? Recently to save on costs, i moved rcn-ee.net from linode to hetzner… While yesterday i did a few reboots due to docker, fingers crossed that didn’t affect you… Most of the images should be now mirrored on beagle’s cloudfair cache…
Regards,
We use a yocto image, start with core-image-minimal. Leave out the dev packages and only add what you need.
That leaves plenty of room and significantly faster boot times. Keep in mind the target market is for buyers on day zero with an embedded device, that means easy entry path, easy entry path means plenty of stuff to facilitate that.
Typically we use a SD card image that is loaded up with code/packages, so huge that it will never begin to fit in emmc. When the project is moved forward you just isolate what is needed to run the binary and add exactly what is needed then move on to a later testing stage after loading it up in emmc.
That is the power of yocto,