Documentation
Getting Started
Documentation Index Installation Details Quickstart
Architecture
Alert Geometry Coverage Data Flow Sequences Design Standards Display System Architecture Eas Decoding Summary Eas Monitor V3 Architecture Sdr Service Architecture System Architecture Theory Of Operation
Development
Agents Certification Reliability Plan Component Library Contributing Javascript Api Sdr Frequency Validation User Interface Guide
Hardware
Alpha Led Guide Argon40 Zigbee Setup Gpio Guide Gps Hat Setup Neopixel Led Control Sdr Setup Serial To Ethernet Adapters Vfd Display Setup Waveshare Rs232 Wifi Setup
Guides
Analytics And Reporting Api Key Management Audio Monitoring Audit Log Review Database Backups Disk Space Cleanup Eas Config Tool Eas Test Signal Pipeline Hardware Quickstart Help Https Setup Icecast Streaming Setup Ipaws Feed Integration Local Mail Server Manual Eas Events Mfa Totp Setup Notifications One Button Upgrade Setup Instructions Smart Setup Ssl Web Ui Guide Tailscale Setup Tts Normalization
Troubleshooting
Firewall Requirements Polling Not Working Sdr Master Troubleshooting Guide Troubleshooting 504 Timeout Tts Troubleshooting Update Not Pulling Changes
Security
Security
Reference
About Changelog Diagrams Ecig Cap To Eas Implementation Guide V1 0 Nws Alert Parameters Ohio Eas Documentation Overview Repository Statistics Vtec Event Linking
Policies
Privacy Policy Sms Messaging Terms Of Use

Disk Space Cleanup Guide

Overview

  1. Container writable layers - Temporary files stored in /tmp before tmpfs was configured
  2. Unused images - Old container images from previous versions
  3. Redis AOF files - Redis append-only file can grow large
  4. Audio archives - Accumulated audio files in /tmp/eas-audio (if enabled)

Before You Start

⚠️ WARNING: These commands will delete data. Make sure you have backups of any important configuration.

✅ Safe to delete: Container writable layers, build cache, old images ❌ Don't delete: The app-config volume (contains your settings)

Step 1: Check Current Disk Usage

# Check overall disk usage
df -h

# Detailed breakdown

Step 2: Stop the Stack

cd /path/to/eas-station

Step 3: Remove Container Writable Layers

This removes accumulated temporary files from container filesystems:

# Remove all stopped containers (this clears their writable layers)

# If you want to be more aggressive, remove ALL containers

This removes cached layers from builds:

# Remove build cache (safe - will be rebuilt on next build)

# More aggressive - remove ALL cache including build cache

Step 5: Remove Unused Images

This removes old container images:

# Remove dangling images (untagged images from old builds)

# Remove ALL unused images (more aggressive)

Step 6: Clean Up Volumes (CAREFUL!)

⚠️ WARNING: This will delete data stored in volumes!

# List all volumes to see what exists

# Remove ONLY unused volumes (won't touch volumes still in use)

# If you want to clean specific volumes (DANGEROUS - read below first):
# DO NOT remove these volumes unless you want to lose data:
# - app-config (your settings - you'll need to reconfigure)
# - redis-data (Redis state)
# - alerts-db-data (your database - you'll lose all alerts)

# Only remove these if you want to start fresh:

Step 7: Complete System Cleanup

All-in-one cleanup command (SAFE - doesn't touch volumes in use):

# This removes:
# - All stopped containers
# - All dangling images
# - All unused build cache
# - All unused networks
# - All unused volumes (only those not attached to any container)

Step 8: Rebuild and Restart

cd /path/to/eas-station

# Rebuild containers (will use less space with tmpfs now)

# Start the stack

# Check disk usage after cleanup
df -h

What the New tmpfs Configuration Does

  1. /tmp directories use RAM: All temporary files in containers are stored in RAM (tmpfs) instead of disk
  2. Automatic cleanup: tmpfs clears on container restart - no manual cleanup needed
  3. Size limits:
    • audio-service: 512MB max
    • sdr-service: 256MB max
    • app: 512MB max
    • pollers: 256MB each
  4. Redis AOF auto-rewrite: Redis will automatically rewrite its append-only file when it doubles in size (max ~128MB)

Monitoring Disk Usage

Add this to your maintenance routine:

# Weekly disk usage check

# Check specific volume sizes

# Monitor Redis data size

Preventing Future Issues

  1. Enable automatic cleanup: Add to your crontab or system scheduler:

  2. Monitor disk space: Set up alerts when disk usage exceeds 80%

  3. Keep audio archiving disabled: Unless you need it for debugging, keep EAS_SAVE_AUDIO_FILES=false

  4. Regular restarts: Restart containers periodically to clear tmpfs:

    # Monthly restart to clear tmpfs

Emergency: Disk Full Right Now

# 1. Stop everything

# 2. Emergency cleanup (removes everything possible)

# 3. Remove ALL containers and images

# 4. Rebuild from scratch
cd /path/to/eas-station

Expected Space Savings

After running these cleanup steps, you should see:

  • Container layers: 20-50GB recovered (depends on how long system was running)
  • Build cache: 5-15GB recovered
  • Old images: 10-30GB recovered (if you have multiple old versions)
  • Unused volumes: Variable (depends on what volumes you remove)

Total expected savings: 35-95GB depending on how long the system has been accumulating data.

Need Help?

If you're still running out of space after cleanup:

  1. Check if redis-data volume is unusually large
  2. Check if alerts-db-data volume has grown large (you may need to archive old alerts)
Back to Documentation Index

This document is served from docs/maintenance/DISK_SPACE_CLEANUP.md in the EAS Station installation.