# Homey Self-Hosted Server (SHS) in VMware Workstation DISK FULL

**URL:** <https://community.homey.app/t/homey-self-hosted-server-shs-in-vmware-workstation-disk-full/160461>\
**Category:** Homey Self-Hosted Server\
**Created:** [October 6, 2026, 8:44pm UTC](https://community.homey.app/t/homey-self-hosted-server-shs-in-vmware-workstation-disk-full/160461 "2026-10-06T20:44:18Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Robert\_1979M](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robert_1979m/32/121015_2.png) [@Robert\_1979M](https://community.homey.app/u/Robert_1979M)\
**Post date:** [October 6, 2026, 8:44pm UTC](https://community.homey.app/t/homey-self-hosted-server-shs-in-vmware-workstation-disk-full/160461/1 "2026-10-06T20:44:18Z")

</div>

Hi all,

I’m running **Homey Self-Hosted Server (SHS) in VMware Workstation** and I’m running into a disk space issue.

Homey is currently running:

- Homey SHS: **13.5.0**
- VMware Workstation
- Virtual disk: **64 GB**
- Linux root partition: only **7.5 GB**
- Filesystem: **ext4**
- `/root/.homey-shs`: only about **165 MB**
- Docker itself reports only one active container.

The problem is that almost all disk usage is coming from containerd:

```auto
/var/lib/containerd ~5.0 GB
/var/lib/containerd/.../overlayfs ~4.7 GB

```

`df -h` shows the root filesystem around **95–97% full**.

I already tried the normal Docker cleanup commands:

```auto
docker container prune -f
docker image prune -a -f
docker system prune -a -f
apt-get clean
journalctl --vacuum-time=7d

```

Docker currently reports:

```auto
Images: 1
Active: 1
Size: 1.322 GB
Reclaimable: 0 B

Containers: 1
Active: 1
Size: 45 KB
Reclaimable: 0 B

```

However:

```auto
du -sh /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs

```

still reports:

```auto
4.7G

```

I also noticed that containerd has a large number of snapshots/container objects:

```auto
ctr -n moby containers ls | wc -l
115

```

but:

```auto
ctr -n moby tasks ls

```

shows only **one running task**.

The snapshot usage shows several large layers, approximately:

```auto
~699 MiB
~698 MiB
~697 MiB
~695 MiB
~685 MiB

```

plus several layers around **249–250 MiB**.

The current Homey container is:

```auto
ghcr.io/athombv/homey-shs:latest

```

and Docker only sees this one container:

```auto
homey-shs

```

My VMware VMDK is already **64 GB** , but the Linux partition is only 7.5 GB:

```auto
/dev/sda 64G
├─/dev/sda1 7.5G ext4 /
├─/dev/sda2 1K
└─/dev/sda5 480M swap

```

So I have plenty of unused space on the virtual disk, but the root partition hasn’t been expanded.

### My questions

1. Is there a **recommended/supported way in SHS to clean old containerd/overlayfs snapshots**?
2. Why does `containerd` have ~4.7 GB of overlayfs data while Docker reports only one active image/container?
3. Are these old Homey image layers safe to remove using `ctr`, or should SHS/containerd handle the cleanup automatically?
4. Is there a recommended procedure to expand `/dev/sda1` from 7.5 GB to use the existing 64 GB virtual disk?
5. Is there anything specific to **Homey SHS** I should do before modifying the partition layout?

I don’t want to manually delete anything from:

```auto
/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/

```

because I don’t want to break the Homey installation.

Any advice from someone familiar with the SHS/containerd setup would be greatly appreciated.

Thanks!

---

<div class="post-metadata">

**Author:** ![Robert\_1979M](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robert_1979m/32/121015_2.png) [@Robert\_1979M](https://community.homey.app/u/Robert_1979M)\
**Post date:** [October 8, 2026, 2:07pm UTC](https://community.homey.app/t/homey-self-hosted-server-shs-in-vmware-workstation-disk-full/160461/2 "2026-10-08T14:07:51Z")

</div>

> [@Diskruimte opgelost in HOMEY SHS ( HOMEY SELF HOSTED ) Hier de HANDLEIDING](https://community.homey.app/t/diskruimte-opgelost-in-homey-shs-homey-self-hosted-hier-de-handleiding/160518):
>
> Homey Self-Hosted Server – disk uitbreiden Ik heb mijn Homey Self-Hosted Server (SHS) draaien op VMware en de virtuele disk vergroot. VMware zag de disk inmiddels als 68,7 GB, maar Linux gebruikte hiervan slechts ongeveer 7,5 GB voor /. Met parted kun je controleren hoe de disk is ingedeeld: Installeer parted: apt update && apt install -y parted sudo parted /dev/sda print free Bij mij zag dat er ongeveer zo uit: Disk /dev/sda: 68.7GB Number Start End Size Type File system 1…