Home » How to Free Disk Space in Proxmox VE by Cleaning Caches and LXC Templates
Systems & Servers

How to Free Disk Space in Proxmox VE by Cleaning Caches and LXC Templates

✨ Quick Answer

The disk space exhausted error on Proxmox VE local storage (No space left on device or VM startup failures) occurs due to the accumulation of obsolete OS installation ISOs, unused LXC templates, old backup dumps, and bloated persistent system logs under the /var/log directory.

Quick Diagnostics

Cause
Proxmox local (root) storage at 100% preventing VM startup
Solution
Delete old ISO images and backups under /var/lib/vz/template/iso/
Cause
Saturated Proxmox log files under /var/log/
Solution
Clean old compressed log files: rm -f /var/log/*.gz /var/log/pve/tasks/*

The disk space exhausted error on Proxmox VE local storage (No space left on device or VM startup failures) occurs due to the accumulation of obsolete OS installation ISOs, unused LXC templates, old backup dumps, and bloated persistent system logs under the /var/log directory.

Step-by-Step Solution

  1. 1

    Step 1: Analyze disk space distribution

    Connect to your Proxmox VE node via SSH and execute a disk space usage check on your local partitions:

    BASH
    # Check disk space on system partitions
    df -h
    
    # Identify directory sizes in default storage locations
    du -sh /var/lib/pve/local-bgs/* /var/lib/vz/*
    
  2. 2

    Step 2: Remove unused installation ISOs and LXC templates

    You can safely clean up operating system installation ISO files and downloaded container templates to recover space instantly:

    BASH
    # Delete obsolete ISOs from the vz storage pool
    rm -f /var/lib/vz/template/iso/*.iso
    
    # Delete unused LXC container template tarballs
    rm -f /var/lib/vz/template/cache/*.tar.xz
    
  3. 3

    Step 3: Vacuum bloated systemd journal logs

    System logs on Proxmox VE can grow to several gigabytes if your virtual machines generate continuous alerts due to hardware or internal network service warnings:

    BASH
    # Force rotation and limit persistent logs to 100 Megabytes
    sudo journalctl --vacuum-size=100M
    

Prevention Advice

Recommended security practices:

  • Do not manually delete virtual disk images (.raw or .qcow2) located directly in the data paths /var/lib/vz/images/ without first removing or detaching them from the Proxmox VE web GUI. Deleting raw disk descriptors manually corrupts the cluster database (pve-cluster), creating logical inconsistencies that block server migration and restore processes.
Author • Web Designer & App Creator

Rodolfo Castro

Web designer, app developer, and founder of SoporteCero. Specializing in UI/UX architecture, digital products, and modern web environments. Every tutorial and guide on SoporteCero is thoroughly tested and verified in our technical lab to ensure reliable, up-to-date solutions.