Unable to update a docker container - no space left on device

[leemarrett]

Hi,

I have proxmox running a few vms - one of them is ubuntu running some docker containers of some web apps.

I'm trying to update one of them and getting "
Pulling 38.1s
failed to register layer: write /usr/share/X11/xkb/geometry/digital_vndr/pc: no space left on device"

but it's a vm with 200gb allocated space and i really don't have that many things on there, nothing that should take up that much space...

How do I figure out what's going on?

when i run df -h i get

Filesystem                         Size  Used Avail Use% Mounted on
tmpfs                              392M  1.9M  390M   1% /run
/dev/mapper/ubuntu--vg-ubuntu--lv   15G   12G  2.1G  86% /
tmpfs                              2.0G     0  2.0G   0% /dev/shm
tmpfs                              5.0M     0  5.0M   0% /run/lock

and then a bunch of NFS mounts...

 

[gfngfn256]

As you can see from within your Ubuntu VM, you are only using 15GB for the created LVM (of the 200GB you claim that VM has).


Assuming your VM actually has that 200GB, the issue is that the Ubuntu OS is not "using" that space in its' LVM.
There are many guides online showing how to get the LVM to do this.
I'll give you a quick overview of the necessary steps required. Note all these actions are from within the VM:

• Firstly show output of lsblk to see the actual disk/partition size.
• Next you may need to repartition/extend that partition to use all of that space. (You can use cfdisk for this).
• Next you will need to extend the Physical Volume (PV) to use that extra space. (You use pvresize & pvdisplay for this).
• Then you will check the Volume Group (VG) for the free space. (Using vgdisplay).
• Next you will check the Logical Volume (LV) for free space & then extend it to use that space. (You will use lvdisplay & lvextend for this).
• Finally you will resize the file system (FS) to those extents. (resize2fs will be used for this).
• When you now check with df -h you should be showing the full size available.

For such actions, make sure you have a full & restorable backup of the VM.

Good luck.