Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsUse the rollback method that matches your deployment: edit the image reference and recreate the affected service with Docker Compose, or run docker service rollback SERVICE on a Docker Swarm manager. Before changing anything, record the exact image digest that was running successfully. A digest identifies immutable image content; a tag such as latest can point to different bytes later.
After the rollback, verify task or container status, logs, health checks, and a representative application request. Reverting an image does not reverse database migrations, schema changes, queue messages, or data written by the failed release, so those require separate recovery decisions.
As an Amazon Associate I earn from qualifying purchases.
First determine whether Docker Compose or Swarm manages the workload
The command is different because Compose manages containers from a project configuration, while Swarm manages a replicated service specification across a cluster. Running the wrong command either fails immediately or changes the wrong object.
| Deployment | Where it runs | Rollback target | Normal recovery action | Network and state considerations |
|---|---|---|---|---|
| Docker Compose | Usually one Docker host | The image reference in compose.yaml or an environment variable |
Restore the previous tag or digest, then run docker compose up -d SERVICE |
Compose replaces the changed container. Mounted volumes are preserved by default, but the replacement can receive a different IP address. |
| Docker Swarm | A service scheduled across a cluster | The service specification saved before the most recent update | On a manager node, run docker service rollback SERVICE or docker service update --rollback SERVICE |
Swarm rolls the service back according to its update and rollback settings; tasks may be recreated on different nodes. |
Useful clues include the commands used to deploy the release and the objects visible from the current host. Compose commands use a project file and service name, such as docker compose ps. Swarm commands use a service name and cluster state, such as docker service ps SERVICE. If you are unsure, do not start by deleting containers. Find the deployment definition first.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
Freeze the incident and capture the last-known-good image
Stop automated deployments and record enough information to reproduce the decision. A rollback is safest when you can state exactly what failed and exactly which image was working before it.
- Freeze further changes. Pause the pipeline, scheduled redeployments, or configuration automation that could immediately put the bad image back.
- Record the service identity. Write down the Compose service name or Swarm service name, host or cluster, container ID or task ID, and deployment timestamp.
- Save the current image reference. Capture the tag or digest shown by the deployment configuration and by the running object. A tag in a file is not proof of the bytes currently running.
- Capture evidence before replacement. Save recent logs, health status, restart counts, and the first symptoms observed by users. This lets you compare the failed and recovered states.
- Find the last-known-good reference. Prefer a registry digest such as
registry.example/app@sha256:<known-good-digest>. If your release process recorded only a tag, verify what digest that tag represented at the time of the good deployment.
Docker describes each tag as representing a digest, similar to a Git hash. The important operational distinction is that tags are names that can move, whereas a digest identifies a specific image manifest. The latest tag is updated often; versioned tags may move less often but are not automatically immutable.
Compose rollback: restore the image reference and recreate one service
For a Compose-managed application, the rollback is a configuration change followed by a targeted recreation. Do not remove the whole project unless you have separately decided that data and unrelated services can be interrupted.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
1. Edit the Compose image reference
Open the same compose.yaml (or alternate Compose file) used by the deployment and change only the affected service. A tag reference looks like this:
services:
api:
image: registry.example/app:previous-versionWhen the known-good digest is available, use digest syntax instead:
services:
api:
image: registry.example/app@sha256:<known-good-digest>If the file obtains the image from an environment variable, restore that variable in the deployment environment instead of changing a generated file that will be overwritten on the next run. Keep the exact spelling, registry hostname, repository, and digest. A digest from a different repository or architecture is not an equivalent image.
2. Make sure the exact image can be obtained
If the known-good image is already present locally, Docker may use it without a registry download. Otherwise pull the immutable reference before recreating the service:
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
docker pull registry.example/app@sha256:<known-good-digest>A failed pull can mean the registry no longer retains that manifest, credentials are missing, the repository name is wrong, or the image was published only for another platform. Do not substitute a similarly named tag merely because it downloads successfully; that can reintroduce different image bytes.
3. Recreate only the affected service
From the directory containing the deployment file, run:
docker compose up -d SERVICEReplace SERVICE with the Compose service name, not the container name. Docker documents that docker compose up stops and recreates a service when its image or configuration has changed. Mounted volumes are preserved by default, so the replacement container can attach to the existing persistent data.
Do not add --renew-anon-volumes casually. That option changes anonymous-volume handling and can discard the data held in those volumes. Review the volume declarations first, especially when the service stores anything that is not reproducible from the image.
4. Reconnect clients through the service name
A recreated Compose container can receive a different IP address. Applications in the same Compose network should use the stable service name, such as api:8080, rather than a container IP. External clients should reconnect through the normal hostname, load balancer, or published port after the replacement becomes healthy. Existing long-lived connections can fail when the old container stops; connection retry logic is expected during this transition.
Swarm rollback: restore the previous service specification
Run a Swarm rollback on a manager node. The command operates on the service’s recorded update history rather than on an individual container.
Use the rollback command
docker service rollback SERVICEThe equivalent update form is:
docker service update --rollback SERVICEDocker’s CLI documentation states that after this command, the service is reverted to the configuration that was in place before the most recent docker service update command. That can restore the prior image, environment, replicas, published ports, and other service settings included in that earlier specification.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
Understand what this rollback does not do
This command rolls back the most recent update recorded by Swarm. It is not a general time machine for every historical deployment. If several updates have occurred since the known-good release, inspect the service history and your deployment records before choosing the recovery path. Do not assume that a tag used by an older deployment still resolves to the same image.
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 & 11Swarm managers resolve an image tag to a digest during a service update, query the registry, and assign tasks that digest. Recording the resolved digest from a known-good deployment gives you a stronger recovery reference than recording only the tag. If you need to deploy a specific older image rather than the immediately preceding service specification, use the exact digest documented by your release process and make that an explicit service update under your normal change controls.
Check the service’s rollout state
After starting the rollback, inspect the tasks and service specification:
docker service ps SERVICE
docker service inspect SERVICETask output shows whether old tasks stopped and replacement tasks reached a running state. Service inspection lets you verify the image reference and the update or rollback policy applied to the service. A task that is merely running is not proof that the application is serving correct responses, so continue with logs, health checks, and an application request.
Tags versus digests: which reference should you restore?
| Reference | What it identifies | Rollback risk | Best use |
|---|---|---|---|
repository:tag |
A human-readable name resolved through the registry | The tag can be moved to a new digest. latest is updated often; versioned tags may also change. |
Convenient development and release labels when your registry policy makes tag movement explicit. |
repository@sha256:digest |
A specific image manifest and its content address | The manifest may be unavailable if registry retention or access is lost. | Incident recovery, production pinning, and any deployment where exact bytes matter. |
Compose image references support both :tag and @digest forms. For incident recovery, write down the digest actually running before you change the service. If the old digest remains on the host, it may be possible to recreate from the local image; if not, pull that exact digest from the registry. Reusing a mutable tag is not equivalent to restoring the old image.
Recommended Free Tools
Validate the rollback before declaring the incident closed
Validation should cover the orchestrator, the container process, and the application behavior. The commands below are operational checks; their output depends on your environment.
Compose checks
- Run
docker compose psand confirm the affected service has the expected state, published ports, and health status. - Run
docker compose logs SERVICE. Look for startup errors, dependency failures, repeated restarts, failed migrations, and messages that indicate the application is still loading the bad configuration. - Inspect the image reference shown by the container and compare it with the recorded known-good tag or digest.
- Exercise a representative request through the same endpoint or workflow that exposed the incident. Check both the response and the application logs generated by that request.
- Confirm that dependent services can reconnect using the Compose service name and that any expected volume data is present.
Swarm checks
- Run
docker service ps SERVICEand verify that replacement tasks are running without a restart loop or rejected state. - Run
docker service inspect SERVICEand confirm the service image reference and replica configuration match the intended previous specification. - Review service or container logs on the nodes hosting the new tasks. Startup success alone does not establish application health.
- Run the service’s health check, synthetic probe, or a representative user request. Include authentication, database access, and any dependency used by the failed code path.
- Watch the service for the full startup and early-operation window used by your team. Some defects appear only after scheduled work, cache warming, or the first real request.
Keep the incident evidence, the restored digest, and the validation results with the deployment record. That information is more useful for the next rollback than a note saying only that the container was restarted.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
What a container rollback does not repair
An image rollback changes executable code and image-level configuration. It does not automatically undo changes made outside the image.
- Database migrations: A newer release may have altered tables, indexes, constraints, or stored data. The older application may not understand the new schema. Decide separately whether a backward-compatible migration, a forward fix, or a tested database restore is appropriate.
- Application data: Records written by the bad release remain in persistent storage. Replacing the container does not remove or correct them.
- External queues and events: Messages already published to a queue or consumed by another service are not rewound by Docker.
- Secrets and environment settings: If the incident came from a changed secret, variable, mount, or configuration file rather than image bytes, restoring the old image alone may leave the failure in place.
- Network clients: A recreated Compose container may have a new IP, and existing connections can be dropped. Use service discovery names or stable front-door endpoints and allow clients to reconnect.
Before sending production traffic back to the old image, check compatibility between that image and every stateful change made by the failed release.
Automatic rollback for future Swarm updates
Swarm supports controls for safer updates and rollbacks, including monitor duration, maximum failure ratio, parallelism, delay, failure action, and operation order. The failure action can be configured to roll back when an update exceeds its failure threshold. Monitoring must last long enough to catch both startup failures and early health failures; a window that ends immediately after process start can report a false success.
Inspect the current policy with the service specification and define the values deliberately for each workload. A stateful database, a stateless API, and a worker may need different parallelism, delay, and monitoring periods. Test the policy in a non-production environment so you know which health and task failures cause Swarm to stop, pause, or roll back an update.
Compose deployment settings for controlled updates
The Compose specification exposes analogous update_config and rollback_config fields, including failure_action, monitor, max_failure_ratio, parallelism, delay, and order. Whether those fields take effect depends on the deployment system honoring the Compose deploy specification; plain local Compose recreation still follows the behavior of docker compose up.
Configure these policies before the next deployment, not during an incident. Select an order that protects availability, a parallelism that limits blast radius, and a monitor period that includes application startup and initial health checks. A rollback policy cannot repair an incompatible database migration, so pair it with backward-compatible schema practices and an explicit data recovery plan.
Troubleshooting common rollback problems
The Compose command recreates the wrong project
Compose determines the project from the working directory, project name, and selected files. Run the command from the deployment directory or provide the same file selection used by the original deployment. Confirm the service name with docker compose config --services before running docker compose up -d SERVICE.
The old tag now starts the same bad image
The tag may have moved in the registry. Compare the image digest, not just the tag text. Restore the recorded digest and pull that exact reference if it is not cached locally.
The digest cannot be pulled
Check registry authentication, repository spelling, platform compatibility, and retention policy. If the registry no longer contains the manifest, locate the archived release artifact or another registry copy. Do not silently replace it with latest or a newly built image and call that a rollback.
Swarm rollback reports no useful recovery
Confirm that you are on a manager node and that the service has a previous update specification. Inspect the service and deployment history. If the desired release is older than the immediately preceding update, identify its exact digest and use an explicitly reviewed service update rather than assuming one rollback will skip multiple releases.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →The container is running but requests still fail
Check health status, application logs, dependency connectivity, credentials, mounted files, and the representative request itself. A process can remain alive while returning errors because of an incompatible schema, missing secret, unreachable database, or failed external dependency.
Clients cannot reconnect after Compose recreation
Replace hard-coded container IPs with the Compose service name for in-network traffic. For external traffic, use the stable hostname or published endpoint. Restart or recycle clients that held connections to the old container, and verify that service discovery has converged.
A concise rollback checklist
- Deployment type identified as Compose or Swarm.
- Deployments frozen and the failing service, container or task, logs, and image reference recorded.
- Last-known-good digest preserved, with registry access confirmed.
- Compose image reference edited and the affected service recreated, or Swarm rollback run from a manager.
- Volumes, migrations, queues, secrets, and other stateful side effects reviewed separately.
- Container or task status, image identity, logs, health checks, and a representative request verified.
- Network clients reconnected through stable service names or endpoints.
- Restored digest and validation evidence attached to the incident record.
The durable lesson is to treat image identity as release data. Tags help people communicate, but a recorded digest lets you restore the exact bytes that were known to work. Combine that identity with the correct Compose or Swarm rollback command and application-level validation, and a bad image update becomes a controlled recovery rather than a guess.
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.
Free tools Windows power users keep installed
One-click scans. No signup required.
