-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Choco is not installed on VM #7704
Comments
Hi @Technomann. Could you share full build log? I assume something went wrong before the lines you have shared. |
This was the very first error:
Sorry, but this is the biggest log I can get, other parts are confidential. |
Well, it doesn't help much. The error you see may indicate that zip file that are extracting is corrupt which may be caused by internet connection issues during download just before. Did you try to re-run build? Do you get this error always or it was just a single occasion? |
Hmm, I understand. It was a single occasion, I did not try a re-run, because it is not a release-marked tag. In pipelines it is more complex to do a rerun anyway. |
Chocolatey is installed using official script: https://chocolatey.org/install.ps1 It downloads Сonsidering the above I'm closing this issue. Feel free to reach out if you have more questions. |
@vpolikarpov-akvelon isn't Chocolatey CLI already installed on the runner image? If so, why the need to attempt to install it again? |
Hey @gep13. You are right, Chocolatey is installed on runners hosted by GitHub. But this thread is about building your own runner from scratch. |
Description
The first error suggests Choco could not be installed on the VM:
Later this is the final error:
The whole error might relate to this error fix:
#7657
Platforms affected
Runner images affected
Image version and build link
Windows Server 2022 20230606.1
Is it regression?
Expected behavior
Creates a VHD in Azure.
Actual behavior
Fails to use Choco
Repro steps
git pull
git checkout win22/20230606.1
User service principal to create VHD in Azure.
The text was updated successfully, but these errors were encountered: