Skip to content

Conversation

@Siumauricio
Copy link
Contributor

  • Updated the backupVolume function to use docker service update --replicas instead of docker service scale for stopping and starting application replicas.
  • This change enhances the backup process by ensuring proper handling of service updates with registry authentication.

What is this PR about?

Please describe in a short paragraph what this PR is about.

Checklist

Before submitting this PR, please make sure that:

Issues related (if applicable)

closes #3403

Screenshots (if applicable)

- Updated the backupVolume function to use `docker service update --replicas` instead of `docker service scale` for stopping and starting application replicas.
- This change enhances the backup process by ensuring proper handling of service updates with registry authentication.
@Siumauricio Siumauricio merged commit af87614 into canary Feb 5, 2026
4 checks passed
@Siumauricio Siumauricio deleted the 3403-volume-backup-restart-fails-for-private-registry-images-missing---with-registry-auth branch February 5, 2026 21:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Volume backup restart fails for private registry images (missing --with-registry-auth)

1 participant