-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Update Mariner build containers #112191
Labels
Comments
This was referenced Feb 5, 2025
Tagging subscribers to this area: @dotnet/runtime-infrastructure |
This will be done with #110199, I hopefully unblocked that one just now. |
Excellent! I knew about that PR but didn't make the connection. Thanks much. If that's the case then you/Sven can add "Fixes: " to that PR so that this issue auto-closes. |
Fixed by #110199 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Mariner 2.0 will go EOL in June 2025. We need to start preparing for that. We should have a strong goal of having no Mariner-based infra by June 1. We've already done a good job of moving most of our infra to Azure Linux 3.0 but there are some images that we didn't get to. That's fine. We did the high pri work first but now need to finish the job.
I was only able to find exposure in
release/8.0
:runtime/eng/pipelines/common/templates/pipeline-with-resources.yml
Lines 51 to 56 in 50773e8
Those are not the only cases. There are others in the same file.
Related:
The text was updated successfully, but these errors were encountered: