Skip to content

Conversation

@shubhamshinde360
Copy link
Contributor

Summary

Services who have restart option set as 'no' are meant to be batch processing jobs which terminate once completed. Docker compose does not restart them, but in the exists? method, puppet looks for a running service. When it is unable to see a running service, it incorrectly assumes non-desired state and makes a corrective change. This commit rejects services with restart 'no' from the compose_services to mitigate this bug.

Additional Context

Related Issues (if any)

Checklist

  • 🟢 Spec tests.
  • 🟢 Acceptance tests.
  • Manually verified. (For example puppet apply)

@shubhamshinde360 shubhamshinde360 requested a review from a team as a code owner February 4, 2026 05:49
…? method

Services who have restart option set as 'no' are meant to be batch processing jobs which terminate once completed.
Docker compose does not restart them, but in the exists? method, puppet looks for a running service. When it is unable to see a running service, it incorrectly assumes non-desired state and makes a corrective change.
This commit rejects services with restart 'no' from the compose_services to mitigate this bug.
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.

1 participant