-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Windows builds broken #8417
Comments
@argoproj/argo-windows can anyone please take a look? |
If I get no reply in 24h, I'll disable the builds. |
Correct. |
Signed-off-by: Markus Lippert <[email protected]>
Signed-off-by: Markus Lippert <[email protected]> Co-authored-by: Markus Lippert <[email protected]>
Signed-off-by: Markus Lippert <[email protected]> Co-authored-by: Markus Lippert <[email protected]>
Signed-off-by: Markus Lippert <[email protected]> Co-authored-by: Markus Lippert <[email protected]> Signed-off-by: Alex Collins <[email protected]>
@alexec @lippertmarkus Dears, The log from wait container is
I also try to change the executor as the following example, But the wait aways run as docker executor. linux Dockerfile had docker cli now. |
I had change my argo-workflow version to 3.3.1, before this change merged, The hello-windows can end with success now. |
@JulianZhang I think you need to set the executor in the global configmap to affect the wait container |
@lippertmarkus Thank you. After change containerRuntimeExecutor from docker to emissary, It works. |
https://github.com/argoproj/argo-workflows/runs/6082729800?check_suite_focus=true
The text was updated successfully, but these errors were encountered: