Yes, same for me. I‘m also not sure if the „unused“ tag is trusty.
I searched by date, older versions and for images that are not installed anymore and deleted them.
By default your Database is stored in /config and called homeassistantv2.db or similar
If you are concerned about unused Docker images, just run docker system prune to remove any unused data.
Found the database:
From where should I run the command (running hassio on PI)
Database is 244 MB. Not that big.
If you can ssh into the OS ( not the hassio container) you should be able to run that command.
Sorry, I do not run the Hassio HassOs image.
I did this, too. But I can freed almost 20 GB by removing unused Docker images manuelly with Portainer.
It only reclaimed a little bit more than 40Mb.
I need to figure out what is consuming the disk space.
What size is your disk and how does that compare with the total disk space output of df -hl ?
Your system may not be making use of all the disk space.
It looks like it is using all your card.
You now need to figure out what is using the space. Sometimes logs pr camera images can consume a lot.
Yes I agree @anon34565116, question is how I can discover that. Currently I do not use camera’s. The majority of my integrations is Chromecast, XBOX and PS4
Any tips are welcome
I do not know what commands are available in HassOS.
It apparently has dh. Does it have du (disk usage) ?
If I feel like guessing I would try du -sh /usr/share/hassio. If that looks like the large usage. you can cd down from there, looking for the culprit.
Otherwise. cd / ls to list the direcories there & try du -sh for each one of then, avoiding proc & dev. They are special and would likely hang.
Just at a guess and not being too familiar with Hassio it looks like multiple instances of Hassio are installed on that card. I may be way off but the partitioning definitely looks suspect.
I’d take a snapshot of my setup, clean that card and start from fresh. As @anon34565116 mentions randomly deleting files not knowing what files you are deleting is Russian roulette. It probably won’t end well.
That is a possibility too.
Try this command to clean up but be sure Hassio is running first. docker system prune This cleans up any old or unused images.
If Hassio is stopped it will get deleted too, so be careful 
I ran the docker system prune command before, and did it again without a major result. Why do you think multiple hassio images are on this SD storage card @ConcordGE?
The prune command doesn’t result in extra disk space now. I will use the commands to find out where the disk space is used.
It was a good observation. I was just saying how to reclaim that space. Mu cheap Docker training is good for something, I guess 
My thinking was that instead of updating, the Docker was being installed on each attempt to update. Again I’ve only installed the Docker in the last couple of days on a test rig to see what all the fuss was about but to be honest I haven’t even looked at it yet.
Docker normally just downloads a new image when upgrading. The older ones are still there but stopped unless Hassio has a cleanup job.
