Lolevel
opened 4 months ago
-
If your job executor is docker based, while some command steps of your job is not docker based, the executor will not be applicable. This also happens if your job contains some privilege steps (publish site, publish html report), and privilege option is not enabled for your executor.
The websocket error you see from agent to server should not cause the not applicable error. To solve this issue, make sure to configure reverse proxy side of OneDev server to allow websocket traffic (https://docs.onedev.io/administration-guide/reverse-proxy-setup).
-
Thank you for your support! The issue was on my side: I had added steps to my build spec that cannot be executed from inside the Docker container. That caused the executor to become not applicable for my jobs. Everything is working as expected now. Thanks again for your fast response!
-
Previous Value Current Value Open
Closed
| Type |
Question
|
| Priority |
Normal
|
| Assignee | |
| Labels |
No labels
|
I created a job executor and an agent in OneDev and successfully created and ran jobs using them. However, suddenly I started receiving the error message:
"Specified job executor 'runner' is not applicable for current job"
"runner" is the name of my job executor.
Nothing was changed in the executor configuration before this started happening. The agent logs indicate repeated connection failures with errors like connection refused and "502 Bad Gateway" during WebSocket upgrade attempts.
It seems the agent is unable to maintain a proper connection to the server, causing OneDev to mark the executor as unusable for running jobs.
Please help to diagnose why the runner is no longer considered applicable despite no changes on my side, and advise on resolving the connectivity issue between the agent and the server.