-
Notifications
You must be signed in to change notification settings - Fork 83
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
Failures to download install script in CI #582
Comments
Cc @mairaw the redirect from the website seem to be failing - are there metrics or configuration that we need to dig into? This has also been hitting internal MS teams this morning. |
We seem to be getting better luck downloading directly from GitHub from: https://raw.githubusercontent.com/dotnet/install-scripts/refs/heads/main/src/dotnet-install.ps1 (Accessible via the "Raw" button on the top right of a file) e.g. curl.exe -sL https://raw.githubusercontent.com/dotnet/install-scripts/refs/heads/main/src/dotnet-install.ps1 > dotnet-install.ps1 or wget https://raw.githubusercontent.com/dotnet/install-scripts/refs/heads/main/src/dotnet-install.sh -O dotnet-install.sh |
As a workaround you can use |
As I said internally @baronfel, this doesn't hit the website. This is a routing service handled by the CPS Engineering team. I've alerted them of the problem, and they told me they've been fixing the issues they're seeing. But this shouldn't be assigned to me since I can't fix this. |
This has been happening with increasing frequency. Source is ADO Pipeline.
https://github.com/dotnet/dotnet-docker/blob/main/documentation/scenarios/installing-dotnet.md#installing-from-dotnet-install-script
#20 [base 5/19] RUN curl -sSL https://dot.net/v1/dotnet-install.sh > dotnet-install.sh
#20 18.35 curl: (18) HTTP/2 stream 1 was not closed cleanly before end of the underlying stream
#20 ERROR: process "/bin/sh -c curl -sSL https://dot.net/v1/dotnet-install.sh > dotnet-install.sh" did not complete successfully: exit code: 18
I'm going to add some retry. Is there a problem with the hosting? Could equally be an ADO thing.
The text was updated successfully, but these errors were encountered: