Docker / Compose, Swarm & Production Security
Inspect a Swarm rolling update that paused or rolled back
A service update can stop progressing when replacement tasks fail its configured policy. Capture status and update settings.
Environment and inputs: Docker Engine · Compose v2 and Buildx where specified; Linux containers unless noted. Verify daemon context, installed feature support and authorized host or Swarm manager access first.
Start with this check
Confirm the environment and replace sample objects, namespaces, images, paths and hosts with approved targets. Share only relevant, sanitized output. Follow the workload owner’s process for changes.
docker service inspect --format '{{json .UpdateStatus}} {{json .Spec.UpdateConfig}}' webRead the result
The values describe recorded update progress and policy. Task errors and application health provide the underlying failure context.
Resolve and verify
Compare the failed image, resources and health timing with the approved release. Repair the cause and resume or roll back through a reviewed compatible plan.
Before changing production
Do not disable failure handling or assume a service-spec rollback undoes persistent-data migrations.