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?
@mcrmonkey https://community-scripts.github.io/ProxmoxVE/scripts?id=debian-13-vm&category=Operating+Systems
Looking back I can see it does mention some "tips after installation" so I did miss that.
🆎
ant