zwZjut opened a new issue, #10051: URL: https://github.com/apache/dolphinscheduler/issues/10051
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues. ### What happened [Bug] [deploy on k8s ] worker server and alert server always crash curl not found in worker Warning Unhealthy 33m (x641 over 14h) kubelet Readiness probe failed: OCI runtime exec failed: exec failed: container_linux.go:380: starting container process caused: exec: "curl": executable file not found in $PATH: unknown Warning BackOff 8m12s (x2238 over 14h) kubelet Back-off restarting failed container Warning Unhealthy 3m23s (x573 over 14h) kubelet Liveness probe failed: OCI runtime exec failed: exec failed: container_linux.go:380: starting container process caused: exec: "curl": executable file not found in $PATH: unknown alert crash without log kubelet Back-off restarting failed container ### What you expected to happen [Bug] [deploy on k8s ] worker server and alert server always crash curl not found in worker Warning Unhealthy 33m (x641 over 14h) kubelet Readiness probe failed: OCI runtime exec failed: exec failed: container_linux.go:380: starting container process caused: exec: "curl": executable file not found in $PATH: unknown Warning BackOff 8m12s (x2238 over 14h) kubelet Back-off restarting failed container Warning Unhealthy 3m23s (x573 over 14h) kubelet Liveness probe failed: OCI runtime exec failed: exec failed: container_linux.go:380: starting container process caused: exec: "curl": executable file not found in $PATH: unknown alert crash without log kubelet Back-off restarting failed container ### How to reproduce . ### Anything else . ### Version dev ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
