There is no single Docker command that safely updates every container on a Linux server. For containers managed by Compose, update each project with docker compose pull followed by docker compose up -d. Compose downloads newer service images and recreates services whose image or configuration changed. Repeat the process for every Compose project. Containers created with standalone docker run need to be recreated from their original settings, because Compose cannot discover their mounts, ports, networks, environment variables, or restart policies.
Antihost offers VPS plans with one-click Docker, NVMe storage and a 14-day free trial.
The correct update command depends on how each container was created
Docker containers do not all share one update mechanism. A server may contain several independent Compose projects as well as containers created manually with docker run. Treat each group according to its management method.
As an Amazon Associate I earn from qualifying purchases.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstall| Container type | Update method | Scope |
|---|---|---|
| Compose project | docker compose pull, then docker compose up -d |
Only services in the selected Compose file/project |
| Compose project requiring every service to be recreated | docker compose up -d --pull always --force-recreate |
Every service in the selected project |
Standalone docker run container |
Pull the replacement image and run a new container with the original configuration | One manually managed container at a time |
| Automated updater | An updater such as Watchtower polls image registries and recreates selected containers | Its configured container selection, often all running containers by default |
Use the Compose workflow as the default for services defined in version-controlled Compose files. It gives you a repeatable configuration, a review point before restarting services, and a clear project boundary.
Before pulling any image
An image update can change application behavior, required configuration, database schemas, or supported environment variables. Prepare the server before starting a maintenance window.
#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.
Inventory every project
Find each compose.yaml, compose.yml, or equivalent file and record which services belong together. A common layout has one directory for a game server, another for monitoring, and another for a database-backed application. Those are separate projects even when they run on the same host.
For a Compose file outside your current directory, use the -f option:
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →docker compose -f /path/to/compose.yaml ps
You can also select a file through the COMPOSE_FILE environment variable. Make sure the command uses the same environment variables and override files as the original deployment; otherwise Compose may resolve different image names, ports, volumes, or secrets.
Confirm backups and persistent storage
Back up databases and important files in bind mounts or named volumes before replacing images. Normal Compose recreation preserves mounted volumes, but preservation is not a substitute for a tested backup. A new application image may perform a one-way database migration, expose a software bug, or require a different data format.
- Confirm when the latest database backup completed and where it can be restored.
- Check bind-mounted directories for sufficient free space and correct ownership.
- Identify named volumes that contain saves, configuration, uploads, or databases.
- Record any service-specific migration or upgrade notes supplied with the image.
Review image references and credentials
Look at every image: entry. Mutable tags such as latest can point to a different image digest without changing the Compose file, while version tags or digests make the selected release easier to audit. Confirm that private-registry credentials are available before the pull and that the host can resolve and reach the registry.
Read the release notes for major version changes. Check for renamed environment variables, changed ports, new required capabilities, altered health checks, and migration commands. Pulling an image does not automatically update application code baked into a separate custom image; that image must be rebuilt when its source changes.
Step-by-step: update one Compose project
1. Open the project directory or select its file
Change to the directory containing the Compose file:
cd /srv/my-project
Then verify the project and its current container state:
docker compose ps
If the file is elsewhere, keep the project directory as your working directory or pass the file explicitly on every command:
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
docker compose -f /srv/my-project/compose.yaml ps
2. Pull the service images
Download images referenced by the selected project:
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minutedocker compose pull
With an explicit file:
docker compose -f /srv/my-project/compose.yaml pull
This command pulls service images; it does not recreate or restart the containers. Review the output for authentication errors, missing tags, rate limits, or a registry connection failure before proceeding.
3. Recreate changed services in the background
Apply the pulled images and run the project detached:
docker compose up -d
Compose creates and starts services. If a service image or configuration changed, it stops the old container and recreates it. The -d option leaves services running in the background and returns control of the terminal.
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 →For a file outside the current directory:
docker compose -f /srv/my-project/compose.yaml up -d
4. Force recreation when required
If you need every service in this project recreated, even when Compose does not detect a change, run:
docker compose up -d --force-recreate
To make this same command check the registry for every service before starting:
docker compose up -d --pull always --force-recreate
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)
The equivalent explicit-file command is:
docker compose -f /srv/my-project/compose.yaml up -d --pull always --force-recreate
--force-recreate affects recreation, while --pull always sets the image-pull policy for that invocation. They solve different problems and can be used together.
5. Verify the result
Do not treat a successful command exit as proof that the application is healthy. Check the project immediately:
- Run
docker compose psand confirm expected services are running and, where configured, healthy. - Read recent output with
docker compose logs --tail=100or target a service withdocker compose logs --tail=100 service_name. - Test the exposed endpoint, game connection, administrative interface, or API from an appropriate client.
- Confirm scheduled jobs, workers, queues, and dependent services continue processing.
- Check disk space, memory use, and restart counts if a service repeatedly exits.
Keep the previous image digest and the exact Compose configuration available during the observation period. That information is essential if a rollback becomes necessary.
6. Repeat for every project
Run the same pull, recreate, and verification sequence for each independent Compose file. A command issued in one project does not inspect or update containers belonging to another project.
What each Compose command actually changes
| Command | What it does | What it does not do |
|---|---|---|
docker compose pull |
Downloads the images referenced by services in the selected project. | Does not recreate or restart running containers. |
docker compose up -d |
Creates and starts services in the background; recreates a service when its image or configuration changed. | Does not affect unrelated projects or arbitrary docker run containers. |
docker compose up -d --force-recreate |
Forces every service in the selected project to be recreated. | Does not itself create a database backup or perform an application migration. |
docker compose up -d --pull always --force-recreate |
Always checks for newer images for this run and recreates every service. | Does not make the operation safe for incompatible application releases. |
docker compose start |
Starts containers that already exist and are stopped. | Does not pull new images or create replacement containers. |
Docker documents that mounted volumes are preserved during normal Compose recreation. The container filesystem itself is disposable, so data that matters must be in a named volume or bind mount and covered by a backup plan.
Updating several Compose projects without taking down the whole server
Update projects independently rather than issuing one broad stop command. This limits the maintenance window and avoids restarting unrelated services.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- List the projects and their service dependencies.
- Choose one project and announce or schedule its interruption.
- Run the pull, recreate, and verification sequence for that project.
- Wait for health checks, background workers, and dependent clients to stabilize.
- Proceed to the next project only after the first has passed its checks.
A reverse proxy, shared database, or network used by several projects may create dependencies that are not obvious from one Compose file. Update a shared dependency only after confirming that its clients support the new version, and avoid restarting a database and all of its clients simultaneously unless the maintenance plan requires it.
Why docker compose down is usually unnecessary
docker compose up -d can stop and recreate changed services without first removing the entire project. That normally creates a smaller change window and leaves project resources in place. Use docker compose down only when you deliberately need to remove the project’s containers and networks or when a documented recovery procedure calls for a full teardown.
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
Before using down, understand which resources it removes and ensure that persistent data is stored outside the disposable container layer. Removing a project is not a substitute for upgrading an image and can make recovery slower.
Updating containers created with docker run
Standalone containers are not represented by a Compose file, so there is no universal safe one-line update command. The original run configuration must be reproduced: environment variables, bind mounts, named volumes, published ports, networks, labels, restart policy, capabilities, entrypoint, command, and any device access.
Capture the existing configuration first
List running containers and identify the target:
docker ps
Inspect its low-level configuration before changing anything:
docker inspect container_name
Record the image reference and digest, mounts, port bindings, networks, environment, restart policy, entrypoint, command, user, capabilities, and labels. If the original shell command was recorded in deployment notes or system administration history, preserve that as well; inspection output is detailed but is not always a ready-to-run replacement command.
Pull and recreate the container
- Back up the container’s persistent data.
- Pull the intended replacement image with
docker pull image:tag. - Stop the old container with
docker stop container_name. - Remove only the container object with
docker rm container_name; do not remove its named volumes. - Run a new container using the recorded mounts, ports, networks, environment variables, restart policy, entrypoint, and command.
- Check logs, health, exposed ports, and application behavior before deleting the previous image.
If the replacement fails, keep the old image and configuration available. Recreate the container from the previous image reference while preserving the same volumes and network settings. Never assume that rolling back the image alone reverses a database migration; follow the application’s documented downgrade or restore procedure.
Move important standalone services into Compose
For a long-lived or business-critical service, encode its configuration in a version-controlled Compose file. This makes image changes, environment files, mounts, networks, and restart policies reviewable and gives you the safer pull and up workflow. Migration itself should be planned as a separate change: export data, reproduce the current settings, test the new project, and keep a recovery path.
Recommended Free Tools
Data safety, migrations, and rollback planning
Image replacement and data migration are separate operations. A container can start successfully while an application is still incompatible with its existing data, or it can alter a schema before a later health check fails.
- Take a restorable backup before the update, not merely a filesystem copy whose consistency is unknown.
- Read release notes for migration requirements and required startup order.
- Use a maintenance window when clients cannot tolerate a brief restart.
- Keep the previous image digest, Compose file, environment files, and volume names.
- Define the rollback trigger: failed health checks, error-rate increase, lost saves, broken authentication, or incompatible clients.
- Test the rollback procedure on a non-production copy when possible.
During a rollback, stop the affected service, restore the previous image and configuration, and restore data only when the application requires it. If a migration is irreversible, a database backup may be the only reliable rollback mechanism.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Automatic updates with Watchtower
Watchtower is an optional containerized updater for operators who accept unattended image pulls and restarts. Its documented default deployment monitors all running containers, checks for updated image digests every 24 hours, pulls a newer image, gracefully stops the target container and its dependencies, and starts a replacement while maintaining the previous container configuration.
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.
Automatic updating changes the operational model. Instead of choosing a maintenance window and reviewing release notes, you allow an updater to act when a registry digest changes. Watchtower also supports container-selection controls and a monitor-only mode, which can be used to identify updates without applying them immediately.
Free tools Windows power users keep installed
One-click scans. No signup required.
| Decision factor | Manual Compose workflow | Automatic updater |
|---|---|---|
| Maintenance timing | Operator chooses the window and order. | Restarts occur according to the updater’s polling and selection rules. |
| Release review | Images and release notes can be reviewed before recreation. | Requires separate controls or a monitor-only process to defer application. |
| Scope | Explicitly limited to one Compose project or one selected container. | Depends on configured selection; a default deployment may monitor all running containers. |
| Rollback | Previous digest and configuration can be retained deliberately. | Needs an explicit image-retention, backup, and rollback design. |
| Operational burden | More hands-on work for every project. | Less routine work, but more risk from unexpected restarts or incompatible releases. |
| Monitoring | Verification is part of the update procedure. | Requires health checks, alerts, and logs so a failed unattended update is noticed. |
Before enabling automatic updates on production services, define backups, health checks, maintenance windows, image-tag policy, notification, and rollback rules. Automatic recreation cannot compensate for an untested restore or an application that requires a coordinated migration.
Troubleshooting common update failures
The image pull is denied or cannot find a tag
Check the image name and tag in the Compose file, authenticate to the private registry, and verify that the tag exists for the server’s architecture. Do not continue to recreation until every required service image has pulled successfully.
The command says everything is up, but the old version is still running
Confirm that you ran the command in the intended project and that the service’s image reference actually changed. Run docker compose ps and inspect the service image. A running container created by another Compose file or by docker run will not be changed by the current project command.
A service exits immediately after recreation
Read its logs, inspect health-check output, and compare environment variables, mounts, ports, and command settings with the previous configuration. Common causes include a required variable removed in the new release, a failed migration, a port already in use, or permissions changed on a bind mount.
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 →Dependent services fail during the restart
Check startup order, health checks, network membership, and connection settings. Restart only the affected project when possible. If several projects share a database or proxy, verify that the shared service remained available and that clients reconnect after the replacement.
There is not enough disk space
Images, old container layers, and logs can consume space during an update. Confirm which images and volumes are in use before removing anything. Never delete a volume merely because it is not attached to the newly created container; it may contain the only copy of persistent data.
A repeatable maintenance checklist
- Inventory every Compose file and standalone container.
- Identify project dependencies and choose a maintenance window.
- Verify restorable backups for databases and important mounted data.
- Review image tags, release notes, credentials, migrations, and architecture support.
- Run
docker compose pullfor one project. - Run
docker compose up -d, or use--pull always --force-recreatewhen those behaviors are required. - Check service state, health, logs, endpoints, jobs, and dependent clients.
- Record the new image digests and retain the previous configuration for rollback.
- Repeat for each Compose project.
- Recreate standalone
docker runcontainers from their recorded settings instead of assuming Compose will find them.
Bottom line
For a Compose-managed project, the dependable update sequence is docker compose pull followed by docker compose up -d. Add --pull always --force-recreate when you need the start command to check the registry and recreate every service. Run that workflow separately for every Compose project, protect persistent data with backups, and verify the application after each restart. Standalone containers require manual recreation from their original configuration, while automatic tools such as Watchtower should be enabled only after backup, health-check, maintenance-window, and rollback rules are explicit.
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.
