Free tools Windows power users keep installed
One-click scans. No signup required.
A reliable Docker cleanup job should remove only objects that have exceeded a deliberate retention period, leave volumes alone unless you have classified them, and record what changed. For most small Linux VPSs, begin with a root-owned script that runs docker system prune --force --filter 'until=168h' once a day or once a week. The seven-day window is a starting policy, not a universal safe value: extend it when you depend on locally cached images for rollback.
Antihost offers VPS plans with one-click Docker, NVMe storage and a 14-day free trial.
What Docker cleanup removes—and what it deliberately leaves behind
Docker does not continuously delete most unused objects. Cleanup is an explicit operation, so a host can accumulate stopped containers, old images, unused networks, and build cache until the filesystem is full.
As an Amazon Associate I earn from qualifying purchases.
The default system-level command is:
docker system pruneWith confirmation disabled and an age filter, the routine form is:
docker system prune --force --filter 'until=168h'This targets eligible stopped containers, unused networks, dangling images, and unused build cache. It does not remove volumes unless you explicitly request volume pruning. Running containers are not the target of this cleanup.
#1 Best Overall
- BLUE LIGHT BLOCKING GLASSES: Our blue light glasses for women boast UV400 protection, blocking harmful blue rays from computer screens. With these bluelight glasses women, you can enjoy gaming, reading, or watching TV with no worries of eye strain.
- EYE RELIEF: Our blue light glasses are engineered to reduce blurry vision or strain caused by prolonged screen time. These womens blue light glasses aid in better sleep by preventing blue light from disrupting your natural sleep cycle, helping you fall asleep faster and enjoy a more restful night's sleep, making them the perfect christmas present.
- COMFORTABLE: Crafted from durable material, our trendy blue light glasses for woman or blue light glasses men ensure long-lasting comfort. The high-transmittance lenses accessories, gamer gifts for men, help keep your eyes relaxed. Perfect stocking stuffers, gifts for gamers men, christmas gifts for men, halloween costumes.
- LIGHTWEIGHT: These clear blue light glasses feature a lightweight frame, meaning they’ll stay comfy for long-term wear. Perfect as blue blockers glasses for women or mens blue light glasses, these non-prescription fake glasses for men can be worn throughout the day. The blue light blocking glasses women feature polycarbonate HD lenses, which are anti-reflective and restore true color.
- WORRY-FREE PURCHASE: If you experience any issues, our support team is ready to assist you quickly. These are the perfect costume glasses for cosplay dressing up.
| Object | Included in ordinary system prune? |
Important qualification |
|---|---|---|
| Stopped containers | Yes | Only objects meeting the filter are eligible; a stopped container needed for inspection or rollback can still be removed. |
| Unused networks | Yes | Networks not attached to a container are candidates. |
| Dangling images | Yes | These are untagged image layers not referenced as needed by a container. |
| All unreferenced images | No | Add -a (or --all) to delete images not referenced by any container. |
| Build cache | Yes | General system pruning can reclaim eligible cache; use Buildx-specific controls when cache is the main consumer. |
| Volumes | No | Volumes are intentionally excluded because they may contain persistent application data. |
Because Docker leaves volumes out by default, a routine system prune is materially safer than a command that includes --volumes. The trade-off is that persistent data and unused volume storage require a separate inventory and policy.
Choose a cleanup policy before scheduling anything
Automation turns a one-time command into an irreversible recurring decision. Define what “unused” means for your deployments, how long rollback artifacts must remain available, and which objects are disposable. The following policies cover the common choices.
Conservative system cleanup
Use this as the initial policy on a small VPS:
docker system prune --force --filter 'until=168h'The until=168h filter expresses a seven-day age window. Eligible stopped containers, unused networks, dangling images, and build cache older than that window can be removed; volumes remain untouched. Observe several cleanup cycles before shortening the window.
Broader image cleanup
Add -a only when every image not referenced by a container is disposable:
docker system prune --all --force --filter 'until=168h'This can delete tagged images that are not currently used by a container. Those images may be the only local copy of a previous release, so a deployment that relies on an immediate rollback can lose that convenience. Keep the rollback requirement inside the retention window or preserve selected images with labels and a separate policy.
Object-specific cleanup
When a single object type is causing pressure, target it instead of pruning the entire system.
Rank #2
- WINDEX GAMING WIPES: effortlessly clean all your gaming gear and gaming electronics in one easy step with our new Windex Gaming Wipes
- AMMONIA FREE: our ammonia-free formula is safe to use on all of your favorite gaming equipment like consoles, headsets, controllers, screens, keyboards, and more
- PRE-MOISTENED WIPES: each wipe instantly removes dust, dirt, and stubborn smudges and fingerprints leaving a streak-free shine
- ANTI-STATIC: great for cleaning and wiping down your gaming gear and electronics leaving behind no visible residue
- COMPACT RESEALABLE PACKAGE: store your pack of Windex Gaming Wipes anywhere in your home for whenever a quick and easy wipedown is needed
| Goal | Command | Scope and risk |
|---|---|---|
| Remove old stopped containers | docker container prune --force --filter 'until=168h' |
Touches stopped containers only; age and label filters are available. |
| Remove old unreferenced images | docker image prune --all --force --filter 'until=240h' |
The --all option includes images not referenced by any container; the ten-day window shown is a policy example. |
| Remove unused anonymous volumes | docker volume prune --force |
Deletes unused anonymous local volumes. Verify that no temporary data is needed first. |
| Remove unused named volumes | docker volume prune --all --force |
A destructive decision. Inventory, labels, and backups should precede it. |
Bounded build-cache cleanup
If build cache, rather than images or containers, is consuming most of the disk, use Buildx pruning:
docker buildx prune --forceBuildx supports limits including max-used-space, min-free-space, and reserved-space. These let you express a cache budget or a minimum amount of free disk instead of deleting cache with an unbounded system policy. Check the installed CLI help for the exact option syntax supported by your Docker version.
Measure the host before and after pruning
There is no universal reclaimed-space figure. The result depends on the host’s images, layers, stopped containers, logs, and cache at the moment the command runs. Capture a baseline so you can judge whether the job is working and whether its retention window is too aggressive.
- Run
docker system df -vto see detailed space usage by images, containers, local volumes, and build cache.
- List all containers, including stopped ones:
docker ps -a - Review local images and their tags:
docker image ls - Inventory volumes before writing any volume policy:
docker volume ls - Record filesystem-level free space with your operating system’s normal disk utility so Docker’s internal accounting can be compared with the actual VPS filesystem.
After a cleanup, run docker system df -v again and retain the output in your root-readable log or system journal. Track free space over several days; a single run cannot show whether a build pipeline is recreating the same cache or whether logs, rather than Docker objects, are the real cause of growth.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Create a root-owned cleanup wrapper
A wrapper gives you a fixed policy, an absolute Docker path, and predictable logging. Create /usr/local/sbin/docker-cleanup as root:
#!/bin/sh
set -eu
/usr/bin/docker system df
/usr/bin/docker system prune --force --filter 'until=168h'
/usr/bin/docker system dfMake it executable and keep ownership restricted:
sudo chown root:root /usr/local/sbin/docker-cleanup
sudo chmod 750 /usr/local/sbin/docker-cleanupThe first and last docker system df calls provide before-and-after observations in the same execution. The script deliberately omits --volumes and -a. Add either only after changing the documented policy and validating the consequences.
Rank #3
- Ergonomic & Adjustable Design: Fight "text neck" and improve your posture. Designed for comfort, it offers an adjustable height (7.1in-8.5in) (1.4in adjustable range) and angle (5°-85°) Please note: cell phone stand is only 9 inches tall—the length of a standard pencil
- Without blocking subtitles Perfect for office desk Tiktok Face Time Zoom video—this is the ultimate kitchen desk essential for phones! Perfect viewing experience while reducing neck back strain, A must-have for gamers streamers desk, and anyone who values both style and support!
- Sleek & Stable Design fits Otterbox Case: Say goodbye to bent cables, tangles, and tip-overs! LISEN’s stylish adjustable desk phone holder features a built-in charging hole and smart cable management, keeping your phone secure and your workspace clutter-free cool gadgets for men
- ANTI-SLIP DESIGN free hands: The under 10.00 items easy gadgets back and the bottom of this kitchen essentials for women are fully covered by anti-skid silicone, which LISEN stand up desk decor can provide maximum protection device from any scratches and slides
- Your Perfect Viewing Companion:If your product arrives damaged or breaks within 365 days, reach out to LISEN for a quick and hassle-free solution. Struggling with assembly, like tightening the screw? We’ve got your back! Your experience matters to us. (Product including: phone Holder stand*1, screw*1, hexagon screwdriver*1, specification*1)
Use the absolute path because scheduled jobs often have a smaller PATH than an interactive shell. If Docker is installed somewhere other than /usr/bin/docker, find the installed location and change the wrapper accordingly. Run the wrapper interactively during a maintenance window or on a staging VPS before enabling automation:
sudo /usr/local/sbin/docker-cleanupRead the output and confirm that the objects selected for deletion match your retention decision. This is an operational safety check; it is not a substitute for backups or a rollback plan.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteSchedule the wrapper with a systemd timer
On distributions that use systemd, a service plus timer provides explicit ordering and journal logs. Create /etc/systemd/system/docker-cleanup.service:
[Unit]
Description=Prune aged Docker objects
Requires=docker.service
After=docker.service
[Service]
Type=oneshot
ExecStart=/usr/local/sbin/docker-cleanupCreate /etc/systemd/system/docker-cleanup.timer:
[Unit]
Description=Run Docker cleanup daily
[Timer]
OnCalendar=daily
Persistent=true
[Install]
WantedBy=timers.targetLoad the units, enable the timer at boot, and start it:
sudo systemctl daemon-reload
sudo systemctl enable --now docker-cleanup.timerVerify scheduling and inspect the service result:
systemctl list-timers docker-cleanup.timer
sudo systemctl start docker-cleanup.service
sudo systemctl status docker-cleanup.service
sudo journalctl -u docker-cleanup.servicePersistent=true allows a missed run to be started after the machine returns, depending on the timer’s calendar behavior. Keep the service as a separate oneshot unit so a failed cleanup is visible as a failed service rather than being hidden inside a shell command.
Use cron when that fits the host’s operations
Cron is adequate when your VPS already centralizes scheduled maintenance there. Install the wrapper in root’s crontab:
Rank #4
- Easy Installation: Our gaming lights have been designed to enhance your entertainment experience. Simply position the led light bar next to your TV or game console to create a game room environment with ease. They come with USB power and a 60 inch cord for direct mounting and mobility
- Audio Syncing & Extensive Mode: The built-in high-sensitivity music sensor allows you to sync the TV led lights to your favorite music. Lights react and move to the beat of music, film and game audio, creating an incredible immersive sound and light experience – and all without the need for an additional hub. You can choose from 64+ patterns, including strobe, illusion, jump, energy, gradient, running, chasing, fluttering mode etc. Each mode can be applied to different scenes
- 64+ Chasing IC+RGB & W Effect: The independent control design of IC+RGB and white all-in-one multifunctional rgbw led bar lights monitor backlight allows you to easily switch the led lights for desk between IC+RGB and white to enjoy a variety of lighting effects, you can choose white lighting mode with high brightness for better illumination when working, etc. Choose IC+RGB lighting mode when you need to create an entertaining atmosphere for the light show, 16 million colours of Color changing rgb light bar let you dance to the beat and create a dynamic party atmosphere
- Dynamic and Dimmable Lights: 1%-full brightness free brightness adjustment gives you the flexibility to adjust dimmable led light bar for room decorations or a variety of occasions
- USB Powered: USB light bars for room can be powered by powernank, usb charger, TV, Monitor, laptop PC mainframe, making behind TV led lighting bar easy to install in any location.TV led lights are powered by the TV usb interface / PC mainframe, can be turned on/off synchronously with TV / PC
sudo crontab -eFor a daily run at 03:00 server time with a root-readable log:
0 3 * * * /usr/local/sbin/docker-cleanup >> /var/log/docker-cleanup.log 2>&1Use an absolute path for both the wrapper and Docker inside the wrapper. Rotate or cap the log so the logging method does not become a second disk-consumption problem. Cron does not provide systemd’s unit dependency ordering or journal integration, so ensure the Docker daemon is available at the scheduled time and investigate nonzero exits.
Protect rollback images with age and labels
The until filter protects recent objects by age, but age alone cannot know that an older release is still required for rollback. Set the retention window from your actual deployment process: if operators may need the previous release for more than seven days, a seven-day prune is too short.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Labels provide a more explicit keep/delete policy when your build and deployment tooling applies stable labels. Docker supports positive and negative label filters for prune commands. For example, a workflow can label an image or container as protected, then exclude that label from a cleanup command. The exact label keys must be consistent across every deployment path; an inconsistent label is not protection.
Before enabling -a, inspect docker image ls and identify which tags correspond to rollback releases, emergency tooling, or offline recovery. If those artifacts are not reproducible from a registry during an outage, retain them locally or copy them to a separately managed backup location.
Treat volumes as application data, not cache
Volumes can contain databases, uploads, queues, and other persistent state. Docker’s default system prune excludes them for this reason. Do not add --volumes to a routine job until every volume has an owner, a purpose, and a tested recovery path.
Best Value
- Compatible with Wide Screens - To ensure compatibility with the dual monitor mount, your each monitor must meet three conditions at the same time: First, computer screens size range: 13 to 32 inches. Second, screen weight range: 4.4 to 19.8 lbs. Third, the back of the monitor screen must have VESA mounting holes with a pitch of 75x75mm or 100x100mm.
- Regarding the compatibility with desks - Your desk must meet three conditions at the same time: First, desk material: Only wooden desks are recommended, plastic or glass desks cannot be used. Second, desk thickness range: 0.59" - 3.54". Third, the bottom of the desk should not have any cross beams or panels, as this will interfere with installation. We recommend carefully checking that your desk and monitors meets all above conditions before purchasing.
- Dual C-Clamp Hold - Worried your dual monitors might wobble or slip? Our upgraded base uses a larger platform plus a dual C-clamp structure to lock the dual monitor arm firmly to your desk. Each arm safely keeps your screens steady while you type, click and game—no shaking, no sliding, just a clean and secure setup you can trust every day. It also provides Grommet Mounting installation choice, both options ensure stable and secure fixation for your 0.59" - 3.54" desk.
- Full-Motion Adjustment For Comfortable View - Pull the screen closer when you’re deep in a spreadsheet, push it back to watch videos, or rotate to portrait for coding — moving everything smoothly with just one hand. The monitor stand offers +85°/-50° tilt, ±90° swivel and 360° rotation. Raise your monitor up to 15.75″ to support a healthy sitting posture. Whether you’re working from home, gaming through the night, or switching between video calls and documents, getting the screens to your natural line of sight helps relieve neck, shoulder and back strain so you can stay focused longer with less fatigue.
- Keep Your Desk Organized: By lifting both screens off the desktop, this dual monitor stand opens up valuable space for your keyboard, notebook, docking station or a simple, clutter-free work area. Built-in cable management guides wires along the arms, keeping cords out of sight and out of the way. Enjoy a tidy, modern workstation that looks as good as it feels to use.
- List volumes with
docker volume ls. - Map each volume to the service or compose project that uses it.
- Check whether the volume is named or anonymous and whether it is currently attached.
- Confirm a current backup and a documented restore procedure for any volume containing application data.
- Only then decide whether anonymous-volume pruning is appropriate or whether named volumes require a separately reviewed, label-based policy.
docker volume prune --force is limited to unused anonymous local volumes. The --all form broadens the operation to unused named volumes and should be treated as a destructive maintenance change, not as a default disk-saving switch.
Recommended Free Tools
Do not confuse object cleanup with log rotation
Deleting images and stopped containers does not remove the log files produced by running containers. Docker’s logging guidance warns that excessive log growth can consume disk space and points operators toward choosing and configuring an appropriate logging driver. Include log usage in the same filesystem investigation as docker system df -v; otherwise a successful prune may appear ineffective because logs are the dominant consumer.
Set a separate log-retention policy appropriate to your daemon and application stack. Test that log rotation actually limits file growth, and monitor the filesystem rather than assuming that container cleanup covers every Docker-related path.
Monitor, alert, and troubleshoot the scheduled job
Alert on disk pressure
Set an alert for low free space on the filesystem that stores Docker data. A cleanup job is a preventative control, not an emergency guarantee: a large image pull or build can consume the remaining space before the next timer run.
Investigate a permission failure
The scheduled process must be able to access the Docker daemon. Running the service as root normally avoids access problems, while an unprivileged cron entry may need membership in the daemon’s access group and an appropriate socket permission. Do not solve a permission error by making the Docker socket or the cleanup script world-writable.
Investigate an unsupported option
Command availability and filter details vary with Docker Engine and API versions. Run:
docker system prune --help
docker container prune --help
docker image prune --help
docker volume prune --help
docker buildx prune --helpCompare the installed CLI’s help with the reference for the matching Engine version before rollout. In particular, volume --all support and some Buildx options can depend on the installed version.
Investigate no reclaimed space
Compare the before-and-after docker system df -v output. Little or no change can be correct when all objects are recent, still referenced, or protected by the filter. It can also indicate that logs, package caches, or another filesystem path—not prune-eligible Docker objects—is consuming the disk.
Investigate a failed deployment after cleanup
Check whether the job removed an image that the deployment expected to use for rollback, or a stopped container that held diagnostic state. Restore from the image registry or backup if available, then lengthen the retention window or add a stable protection label before re-enabling the job. A cleanup command cannot infer operational importance from “unused” status alone.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Quick Recap
A practical rollout sequence
- Inspect containers, images, volumes, cache, and filesystem free space.
- Write down the rollback period and identify any objects that must survive it.
- Start with
docker system prune --force --filter 'until=168h', without-aand without volume options. - Run the root-owned wrapper manually and review its output.
- Enable a daily or weekly systemd timer, or a root cron entry, with logs.
- Compare
docker system df -vbefore and after each run and watch the filesystem trend. - Only narrow or broaden the policy after observing real deployment and rollback behavior.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
