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.
Community Note
Description
When specifying a converge config on a
docker_serviceresource 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)