-
Notifications
You must be signed in to change notification settings - Fork 319
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
Docker plugin stopped starting Docker containers #1087
Comments
I can't duplicate this issue. The agents start reliably for me. If more details become available that make the problem consistently visible, please share that information. |
I face the exact same issue. Sometimes, it works, sometimes doesn't. Environment
I don't know if this can be one of the reasons, but the Cloud statistics shows that there are 3 agents in operation, but there are none. No Windows agents in Nodes and no docker container created in Windows. Restarting Jenkins doesn't takes any effect over it. Is it possible that some caching is causing this? Let me know if you need any logs.... what is the log class that I have to put in the log recorder? |
Same here. Out of blue, controller stops spinning up new docker agent containers. Test connection for cloud node looks good, no significant errors in logs and yet no containers are being spun up. |
Jenkins and plugins versions report
Environment
What Operating System are you using (both controller, and any agents involved in the problem)?
Jenkins master: Oracle Linux 9
Jenkins agents: Oracle Linux 9 + Windows Server 2019
Reproduction steps
The issue cannot be reproduced. In the last couple of months, we had it twice.
Symptoms:
Expected Results
The Docker plugin should react and
Actual Results
No reaction from the plugin. Triggered jobs wait endlessly for their execution as their labels cannot be resolved.
Anything else?
Current workaround: Restarting the complete Jenkins application solves the problem.
Are you interested in contributing a fix?
No response
The text was updated successfully, but these errors were encountered: