Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for error message when service didn't converge #624

Open
dhilgarth opened this issue Jun 3, 2024 · 0 comments
Open

Support for error message when service didn't converge #624

dhilgarth opened this issue Jun 3, 2024 · 0 comments

Comments

@dhilgarth
Copy link

dhilgarth commented Jun 3, 2024

Community Note

  • Please vote on this issue by adding a 馃憤 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

When specifying a converge config on a docker_service resource and the initial deployment of that service fails, e.g. because the container started as part of the service exits right away because of misconfiguration, then there is no way to see the error message, because the provider will delete the service and the failed tasks with it after the converge time is over.

It would be great of the provider could output the last N log lines of the last failed task or so.

New or Affected Resource(s)

  • docker_service
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

No branches or pull requests

1 participant