Hey @SplitIce, looking at the output of ls, it appears that all of the leftover diffs are from July 4th and 5th. It could be possible that the supervisor or balena got into a weird state with a release from around tha time frame.
Can you remember any weirdness going on at around that time? Perhaps a bug in application code that created more data than usual. Regardless this is something that should have been automatically handled, and we’re going to investigate.
In the meantime, a fix for this is to clear out the docker directory. Unfortunately, without knowing which diff is for which container, you’d have to remove the user images and containers too. I can do this for you if you like, with a dashboard link and support access enabled. Alternatively, and for the benefit of the thread, the commands would be:
systemctl stop resin-supervisor
systemctl stop balena
rm -rf /var/lib/docker/{aufs,diff,overlay,containers,image,tmp}
systemctl start balena
update-resin-supervisor