If you run du -h --max-depth=1 in the root directory ( / ) it should show you which directory is taking up so much space. For instance, if you see the directory /var taking up 23Gb, then run the same command inside of the /var directory to see where it is inside of that one.
While it is an overly manual process, this will atleast show you which directory or directories are taking up so much space. From there you can narrow down your troubleshooting to see why something like multiple dockers or your log files (both just examples) are eating up so much space.
One more suggestion to the reference above. Can you add “-a” to the docker system prune command?
That will prune all images that doesn’t have at least one container tied to it. In layman, it prunes a bit deeper than the standard docker system prune command.
Are you running these commands via ssh or via the host itself? If via ssh, your “du” commands are coming from the ssh docker container and not the actual usage of the host.
Here you go, this will help get you to the HOST OS, and not just SSH’ing into the docker container.
I am by NO means a pro at Hassio, so forgive me for redirecting you to another post about this, but I have been a lurker for years, and have picked up a thing or two about the systems. Also know a bit about docker, so that helps, but again don’t take this as punting you to another person/post, it just explains it better than I can.
Use a USB drive formatted with FAT, ext4, or NTFS and name it CONFIG (case sensitive). Create an authorized_keys file (no extension) containing your public key, and place it in the root of the USB drive. File needs to be ANSI encoded (not UTF-8) and must have Unix line ends (LF), not Windows (CR LF). See Generating SSH Keys section below if you need help generating keys. From the UI, navigate to the hass.io system page and choose “Import from USB”. You can now access your device as root over SSH on port 22222. Alternatively, the file will be imported from the USB when the hass.io device is rebooted.
Make sure when you are copying the public key to the root of the USB drive that you rename the file correctly to authorized_keys with no .pub file extension.
You should then be able to SSH into your Hass.io device. On Mac/Linux, use:
You will initially be logged in to Hass.io CLI for HassOS where you can perform normal CLI functions. If you need access to the host system use the ‘login’ command. Hass.io OS is a hypervisor for Docker. See the Hass.io Architecturedocumentation for information regarding the Hass.io supervisor. The supervisor offers an API to manage the host and running the Docker containers. Home Assistant itself and all installed addon’s run in separate Docker containers.
It is definitely the Unifi database and tmp repair database files. So now it is about pruning the database from hassio, how can I do that? Can I access the container SSH into the docker container? Unfortunately I cannot remove files directly from the SD via the mac
I was wondering how did you delete those folders form the Unifi add on, because I am running into the same issue propably. My free disk space is almost 0 .
But I can’t find the folder on the SD card for some reason… any help would be apreciated.
Unfortunately I can’t find where the the disk space is used in my system. I have used the “docker system prune” command but that didn’t make any difference unfortunately.
In portainer I see a lot of “unused” images, but can these be deleted without any problems? i.e. homeassistant/raspberrypi3-homeassistant:0.114.4 is this this the install file from HA?
For now I deleted some backups to free some space.Someone who can help me with this?
Have you checked disk space via host’s terminal? For example by this command (by defining the path you can get more specific folder/file): du -h / --max-depth=1
For me, most of the times, the docker logs are the culprit which eats the disk space. If that’s your case as well, then you can wipe them by: find /var/lib/docker/containers/ -type f -name "*.log" -delete
.
