HASSIO Docker Overlay2 folder consuming all disk space

Tags: #<Tag:0x00007f739288e318>

Same problem here. The overlay2 folder is >12GB in size. What can be done to clean this up and prevent is from happening again in the future ?

I just noticed it because all my commands started failing and my load was very high. This was because no disk space was available anymore.

Look one post above yours.

That did not solve it …

Just checked mine. It’s 14GB.

Isn’t that like, a lot ?
I mean, this means you can’t run the supervised method on a 16 gb card on a rpi …

The recommendation is 32 GB.

I’m having the same issue on a Supervised installation on Ubunto 18. Anyone find a solution for this? I’ve tried pruning already.

I have had this issue with other docker installs. What I discovered was that default linux autopartitioning limits the root partition size (where overlay2 lives) to a fixed amount (I think up to a max of 64GB) and any excess is given to home. So when installing linux you should pay attention to your partition scheme and either allocate more to root than autopart does or just not create a home partition at all.

There are also methods out there to extend your root partition that I have used after the fact by allocating another disk to the VM. But it is better to just start from scratch with a docker friendly partition scheme, if you can, IMHO.

Thanks.
I actually found out that it was another docker container using up my disk space.

On my hassio this command not found.
How you able to run it?

|arch |aarch64|
|chassis |embedded|
|dev |false|
|docker |true|
|docker_version |19.03.8|
|hassio |true|
|host_os |HassOS 4.11|
|installation_type |Home Assistant OS|
|os_name |Linux|
|os_version |4.19.127-v8|
|python_version |3.8.3|
|supervisor |229|
|timezone |Europe/Kiev|
|version |0.113.0|

Same problem here… I try to update home assistant, and it fill my entire disk with more than 20Go of data… I wansn’t abale anymore to login to my openmediavault server…

Did you find something to solve this problem ?

Thanks

Edit : Found it !!! It was the homeassistant database, the file home-assistant_v2.db, which was really heavy because of storing sensor state with a huge refresh rate!
Plus the local snapshot of Home assistant which was saving this huge database!

Same problem on HA 0.114 on Docker, not caused by HA db