Hrfff. So I felt confident enough about my debian VM working to start gently plodding through the Mastodon source install instructions. And it was all going really well until for some reason it looks like my disk is full. What.

Unpacking vdpau-driver-all:amd64 (1.5-3+b1) ...
dpkg: error: failed to write status database stanza about 'libcairo2:amd64' to '/var/lib/dpkg/status': No space left on device
Error: Sub-process /usr/bin/dpkg returned an error code (2)

I gave it 100GB on Proxmox?

Oh but.

root@masto:~# df -h
Filesystem Size Used Avail Use% Mounted on
udev 1.9G 0 1.9G 0% /dev
tmpfs 390M 696K 389M 1% /run
/dev/sda1 2.8G 2.7G 0 100% /

So, when you give a VM a disk size, it doesn't ... use it? Like would make total sense?

I installed my VM using a helper script, I think? And it did ask me how big I wanted it. And I keyed in 100GB. But it seems to have given it 100GB but only used 2.8?

Trash it and try again?

@bloor
Been in a similar situation.
IMO it's quicker to delete the VM and start again than try and fix a failed install.
@AlanJP problem is i'm genuinely also not sure where i went wrong... i did, after all, tell it I wanted 100GB. And it went ahead and , yes, somewhat allocated 100GB (at least in proxmox's mind) but then only made the VM have a tiddly 2.8GB which it then filled.
@bloor
Might be worth trying disk resize method described here:
https://patrickpriestley.com/blog/how-to-resize-vm-drive/
Nothing to lose, apart from some time.
Method uses tools which should already be installed if VM is Debian or Ubuntu.
Guide is quite detailed, including navigating the Proxmox UI to resize the disk.
How to resize an ubuntu vm disk in proxmox

Step-by-step guide to safely resize Ubuntu VM disk storage in Proxmox, including partition expansion and filesystem resizing for ext4 and LVM volumes

Patrick Priestley