-
Notifications
You must be signed in to change notification settings - Fork 10.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
Update build containers #60208
Comments
We don't build native components in those jobs, but the legs using those containers do build node components, so we'd need containers w/ node installed to replace them |
Should we create a pre-req container that is the .NET SDK + node + Helix? Is this for building? It looks like that, but I want to confirm. Also, do you really need a cross image? I assume not. |
Yes, we use the images for building - .NET SDK + node should be sufficient for that. If it was suitable for Helix that'd be nice too as we could use it in multiple places, but wouldn't be necessary for the way we use those containers today. I don't think we need a cross image - we just need images we can build our musl bits on. |
You are right. Helix isn't needed. I was getting my wires crossed. I assume you install the SDK with the install script per the global.json for the branch. Do you just need an image that has .NET dependencies + node in it? |
Yes, that should be sufficient |
I'll make something and let's give it a try. |
Do you think we can get away with a single container image? Specifically, do you need an Alpine variant? Is an Azure Linux x64 image sufficient? |
Having an Alpine variant is nice as that way we can build our musl bits on a musl image - but it's not strictly necessary. I'm fine cross-building if we're trying to slim down our set of docker images. |
I'd much prefer we built everything in Azure Linux images, like we do for runtime. Sounds like it is just a change in approach. If it is a big deal, let's take a closer look. I'll make the Azure Linux image later today. |
Can you give this a shot @wtgodbe? This is beyond my ability to do efficiently. Here's the new image: |
Great. Assuming this works well, I can make .NET 8 and 9 variants of this image so that we can repeat this exercise on the other two active branches. The 10.0 one should work fine, however, it will confuse some people later for no good reason. It is low cost to create the other variants and I'm happy to do that. |
Looks like there was a failure in initializing the container:
|
New error this time:
|
All PRs are merged! |
Thanks @wtgodbe! |
The following container references need to be updated in all active branches.
aspnetcore/.azure/pipelines/ci.yml
Lines 129 to 133 in a4ca931
There are two issues at play:
WithNode
Alpine variantRelated: dotnet/runtime#112191
The text was updated successfully, but these errors were encountered: