-
Notifications
You must be signed in to change notification settings - Fork 976
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to use containers One or more containers failed to start.
#2173
Comments
I won't add our configuration to this comment, but we also encountered the same issue where workflows/jobs reliant on a service (in our case mysql:5.7) were no longer initializing properly due to the service(s) being identified as unhealthy/failing to start. I believe it's likely related to #2110 since reverting our runtime to 2.297.0 (and disabling updates when configuring the runner) caused our workflows to begin working again. |
Ditto - we have seen the issue as well (with mysql, memcache, and redis) The containers are hitting the Thereby failing the job and our workflows. This seems to go against the release notes where it suggests it would use the exit code when a healthcheck isn't configured. |
Double ditto for runner version
And the workflow fails with
|
Hi All, thanks for reporting this issue so fast. We'll be releasing |
Thanks for your patience on this one. If you keep experiencing these service failures on |
I facing this issue today out of the blue |
Describe the bug
This issue happened after version
v2.298.0
was released.Currently, we are unable to use containers in our Workflows.
Error message is a vague One or more containers failed to start.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Should not error initializing Docker containers
Runner Version and Platform
Version of your runner?
v2.298.0
OS of the machine running the runner?
Linux
What's not working?
Please include error messages and screenshots.
Job Log Output
Runner and Worker's Diagnostic Logs
If applicable, add relevant diagnostic log information. Logs are located in the runner's
_diag
folder. The runner logs are prefixed withRunner_
and the worker logs are prefixed withWorker_
. Each job run correlates to a worker log. All sensitive information should already be masked out, but please double-check before pasting here.The text was updated successfully, but these errors were encountered: