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 →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Antihost offers VPS plans with one-click Docker, NVMe storage and a 14-day free trial.
DRY is an interactive terminal application for Docker and Docker Compose. It keeps containers, images, networks, volumes, logs, live statistics and lifecycle actions in one keyboard-driven interface, while still allowing connections to local or remote Docker daemons. Use it when you need fast visual inspection from a shell; use the Docker CLI when the task must be scripted, automated or run headlessly.
What DRY does
DRY (the project is commonly invoked as dry) is distributed as a single binary and presents Docker resources in terminal views. The project README describes it as “a terminal application for Docker and Docker Compose.” Instead of remembering a separate command for every object, you navigate lists and open context-specific actions with the keyboard.
Its coverage includes:
- Containers and their lifecycle state
- Images, networks and volumes
- Docker Compose projects and services
- Container logs, resource statistics and daemon events
- Swarm nodes, services and stacks when the connected daemon runs Swarm
DRY is a client for Docker; it does not replace the Docker daemon. The account running it must be able to reach the selected daemon endpoint and have permission to use that endpoint.
Install DRY and connect it to Docker
Choose an installation method
The project documents several ways to obtain DRY. Pick the method that matches how you maintain software on the machine:
#1 Best Overall
- Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
- With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
- Wide Application: attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
- Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
- Economical &Reusable: Built durable materials with a long-lasting battery,our CAGIWIRU air duster it's a sustainable alternative to disposable air cans.
| Method | What it provides | When it is useful |
|---|---|---|
| Project shell installer | Installs the project’s binary using its documented installer | A quick setup on a supported Unix-like system |
| Downloaded binary | A standalone executable | Minimal installations, servers or controlled rollouts |
| Homebrew | Package-manager installation | macOS and other systems where Homebrew is already managed |
| Arch package | Distribution package | Arch Linux package-managed environments |
| Docker image | Runs DRY in a container while exposing the host Docker socket | Hosts where you prefer not to install a local binary |
The documented Docker-image pattern uses an interactive, temporary container and mounts the host socket:
docker run --rm -it -v /var/run/docker.sock:/var/run/docker.sock moncho/dryThe socket mount is powerful: commands issued in DRY can control the Docker daemon represented by that socket. Treat the mounted socket as administrative access and only run this container where that level of access is acceptable.
Free tools Windows power users keep installed
One-click scans. No signup required.
Understand endpoint selection
DRY chooses a Docker endpoint in this order:
- An endpoint supplied with the
-Hoption - The value of the
DOCKER_HOSTenvironment variable - The local default
unix:///var/run/docker.sock
This order matters when a shell already exports DOCKER_HOST. A command-line -H value takes precedence, while an unset variable allows DRY to fall back to the local Unix socket.
For a local daemon, confirm that the socket exists and that your user can access it before opening the interface. For a remote daemon, verify the host and transport settings independently, then launch DRY with the intended endpoint. A successful DRY start against the wrong endpoint can look like an empty installation even though it is simply showing another daemon.
Check permissions before troubleshooting the interface
- Confirm Docker itself works for the same user by running a basic Docker command.
- Check that the Unix socket path is present when using the default endpoint.
- When using a Dockerized DRY, confirm the socket is mounted inside the DRY container.
- For remote connections, check network reachability and the daemon’s listening configuration before changing DRY settings.
- Do not grant broad socket access casually; Docker socket access generally permits administrative control over the host.
Navigate the container view
Open and refresh the list
Press 1 to open the container list. The list is the central place to select a container and perform inspection, monitoring or lifecycle operations.
Rank #2
- Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
- Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
- Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
- Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
- Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth
F5refreshes the current list.%filters the list so you can narrow a long inventory.F1sorts the current list.
Filtering is especially useful on hosts with many stopped containers. Refresh after starting, stopping or removing a container so the displayed state matches the daemon.
Actions for a selected container
| Key | Action | What to use it for |
|---|---|---|
i |
Inspect | Read the container’s detailed Docker metadata and configuration |
l |
Logs | View application output from the container |
s |
Stats | Open live resource readings |
x |
Execute | Run a command inside the container; the default shell is /bin/sh |
Enter |
Command menu | Open the available actions for the selected container |
Ctrl+r |
Start or restart | Start a stopped container or restart a running one |
Ctrl+t |
Stop | Request a normal container stop |
Ctrl+k |
Kill | Immediately terminate the container when a normal stop is not sufficient |
e |
Remove | Delete the selected container |
Ctrl+e |
Remove all stopped containers | Clean up every stopped container after confirming the destructive operation |
Use the command menu when you are unsure which operation is available for the current state. DRY keeps the resource list visible while you work, reducing the need to copy container IDs between separate commands.
Inspect failures, output and shell state
Inspect configuration with i
Inspection is the right first step when a container exits unexpectedly or exposes the wrong port. Select the container and press i to examine Docker’s metadata. Check its state, image, networking and configured mounts before changing anything. This is safer than repeatedly restarting a container without understanding why it stopped.
Read application output with l
Press l to open the container’s logs. Logs show what the application emitted, which can distinguish an application-level failure from a Docker lifecycle problem. If the output indicates a bad environment variable, missing file or failed dependency, fix that underlying issue rather than cycling the container indefinitely.
Open a shell or command with x
Press x to execute a command in the selected container. DRY uses /bin/sh by default. This is useful for checking files, environment values and connectivity from the container’s own network and filesystem context. Minimal images may not contain a shell or common utilities; in that case, an execution attempt can fail even though the container itself is healthy.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesRank #3
- 【Large size】：Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
- 【LED backlight mouse pad】：Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
- 【Anti-slip rubber base】：Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
- 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
- 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.
Use an interactive shell for diagnosis, not as a substitute for rebuilding an image or correcting its Compose definition. Changes made manually inside a container normally disappear when that container is replaced.
Monitor CPU, memory and daemon activity
Container monitor and live statistics
Press s on a selected container to open its live statistics. DRY’s monitor view exposes status and resource information, and recent release notes describe CPU% and MEM% columns rendered as visual progress bars. The bars make a rapidly changing value easier to scan than a column of numbers, but they are still a point-in-time view: refresh or continue watching when diagnosing a sustained problem.
Use stats to answer questions such as:
- Is one container consuming disproportionate CPU?
- Is memory usage climbing while the application appears idle?
- Did resource use change immediately after a restart or deployment?
Stats show usage; they do not explain the cause. Pair them with logs and inspection so you can relate a spike to a request, configuration change or failing dependency.
Use the global diagnostic views
| Key | View | Best use |
|---|---|---|
F7 |
Docker daemon information | Check daemon-level details when containers behave differently from expectations |
F8 |
Disk usage | Look for storage pressure from images, containers, volumes or other Docker data |
F9 |
Last 10 Docker events | Correlate starts, stops, destroys and other recent daemon activity with an incident |
Logs describe application output, stats describe live container resource use, and events provide daemon-level context. Looking at all three prevents a common mistake: treating an application crash, an out-of-disk condition and an operator-initiated stop as the same problem.
Manage Docker Compose projects
Open project and service views
Press 8 to open Compose projects. DRY can show project services, health, published ports, images and container counts. Select a project to see its services, then drill into a service for logs and lifecycle operations.
Rank #4
- 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
- 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
- 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
- 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
- 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.
Project discovery works from container labels, including labels on stopped containers, or from a Compose file in the directory where DRY was started. Discovery is not recursive. If a project is missing, start DRY in the directory containing the Compose file or verify that the project’s containers carry the expected labels.
Apply service- or project-level actions
Release notes document start, stop, restart and remove operations at both service and project levels. DRY presents confirmation prompts for destructive actions and provides summaries when only some operations succeed. Read the summary instead of assuming that a project-wide action was completely successful: a single service can fail while the remaining services complete their requested operation.
A practical Compose recovery sequence is:
- Open the project with
8and check service health, ports and container counts. - Open logs for the affected service and identify whether the failure is in the application or its dependencies.
- Use a service restart when one service is unhealthy and its dependencies are stable.
- Use a project-level restart only when several services need coordinated recovery.
- Review the operation summary for partial failures, then inspect the specific service that did not complete.
Use DRY with Docker Swarm
When the connected daemon runs Swarm, DRY exposes nodes, services and stacks in addition to ordinary Docker resources. This gives an operator a terminal view of Swarm objects without switching to a separate dashboard.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Remember that the endpoint determines what you see. Connecting to a standalone Docker daemon shows that daemon’s local objects; connecting to a Swarm manager exposes Swarm information. If nodes, services or stacks are absent, verify that you connected to the intended Swarm-aware daemon and that the account has the necessary permissions.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.When the Docker CLI is the better tool
The Docker CLI remains the correct fallback for repeatable, automated or headless work. Docker’s container reference documents commands including:
Best Value
- 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
- 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
- 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
- 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
- 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.
| Need | CLI command family | Why use it instead of an interactive UI |
|---|---|---|
| List containers | docker container ls |
Easy to embed in scripts and filter with shell tools |
| Inspect metadata | docker container inspect |
Produces machine-readable output for automation |
| Read output | docker container logs |
Works in remote sessions and pipelines |
| Run a command | docker container exec |
Explicit, reproducible command invocation |
| Read resource usage | docker container stats |
Suitable for terminal scripts and monitoring jobs |
| Start or stop | docker container start, stop |
Can be placed in deployment and recovery scripts |
| Restart | docker container restart |
Repeatable operational action |
| Remove | docker container rm |
Explicit cleanup in controlled automation |
Docker describes its CLI as scriptable and suitable for automation and headless operation. Use DRY for interactive inspection and quick lifecycle work; use the CLI for CI jobs, scheduled maintenance, incident scripts and any procedure that must produce the same result every time.
DRY versus the Docker CLI: practical trade-offs
| Decision axis | DRY | Docker CLI |
|---|---|---|
| Interaction model | Keyboard-driven navigation with lists and menus | Typed commands that can be composed in a shell |
| Docker object coverage | Containers, images, networks, volumes, Compose and Swarm views in one application | Broad command surface, including operations not exposed in DRY’s menus |
| Logs, events and stats | Dedicated interactive views, including daemon events and visual CPU/MEM bars | Separate commands that are easy to redirect or parse |
| Compose management | Project and service navigation with lifecycle actions and partial-failure summaries | Explicit commands suited to deployment files and automation |
| Remote daemon use | Uses -H, DOCKER_HOST or the local socket according to its precedence rules |
Uses Docker’s endpoint configuration and command options |
| Destructive operations | Confirmation prompts and visible context before removal | Scriptable and precise, but safeguards must be designed into the command or script |
| Installation footprint | Single binary, package or Docker image | Docker CLI installation already present on most Docker hosts |
The available primary documentation does not provide an authoritative performance benchmark comparing DRY with the Docker CLI or another dashboard. Choose based on workflow and operational requirements rather than an unverified speed claim.
Common problems and recovery steps
DRY shows no containers
- Press
F5to refresh. - Check the endpoint precedence: a command-line
-Hor exportedDOCKER_HOSTmay point to another daemon. - Confirm Docker permissions for the current user.
- If you expected a Compose project, remember that discovery is not recursive and that DRY must start in the directory containing the Compose file when labels are not available.
A container action fails
Open the container with i, review its state and then check l for application output. A stop may be refused or delayed by the application; a kill is immediate and should be reserved for cases where normal shutdown is not working. For removal failures, check whether the container is still running or referenced by another operation before retrying.
Stats or logs appear stale
Refresh the view and confirm that you are watching the intended container. Stats are live readings, while logs depend on what the application writes. Use F9 to check recent daemon events when the displayed state does not match an action you just performed.
A Compose project is incomplete
Check whether all services have been discovered, including stopped containers. Verify the working directory used to launch DRY and inspect the project’s service labels. After a project-level action, read DRY’s operation summary: a partial failure identifies which service needs separate inspection.
A safe daily workflow
- Verify the endpoint and permissions before making changes.
- Open the container list with
1, filter with%and refresh withF5. - Inspect configuration with
ibefore restarting a failing container. - Read logs with
land watch resource use withs. - Use
xfor temporary in-container diagnostics, remembering that manual changes are not durable image changes. - Choose start, restart, stop, kill or remove deliberately; use the confirmation prompt as a final safety check.
- For Compose, use
8, inspect service health and review partial-failure summaries. - Use
F7,F8andF9when the problem appears daemon-wide rather than application-specific. - Translate a proven manual fix into Docker CLI commands when it must run repeatedly or without an interactive terminal.
That division of labor is DRY’s main value: it gives an operator a fast, contextual terminal control panel, while Docker’s CLI remains the dependable interface for automation and reproducibility.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Quick Recap
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.
