-
Notifications
You must be signed in to change notification settings - Fork 1.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
[Arm64/Linux] 3.0 docker images #504
Comments
cc/ @etherealjoy |
@sdmaclea
I tried creating the images from the tar files from the master build , and it runs sometimes and sometimes it does not. Usually there is an error from roslyn.compilers.csharp .targets or something and exit. I am using linux-arm64 as rid. If you guys build it I would test it asap. I mean TFM 2.2 is available now right? |
This is on our radar but our plates are rather full at the moment with a few upcoming releases. The main work for us is to get build and ci machines in place. I would hope in a couple weeks we will have builds available in the nightly repo. |
@MichaelSimons
Including aspnet core? |
@etherealjoy - I can't comment on ASPNET.Core. Obviously aspnet/Universe#1117 is a requirement. |
@MichaelSimons |
The last daily linux-arm64 cli build I tested, was failing with a segmentation fault in csc.dll. I wanted to check to see if it was working on x64. However, when I looked at yesterdays daily build status, everything was red, so I didn't bother debugging further. Last I looked ASP.NET build support was included in the CLI. So you should be able to build ASP.NET core projects for arm64. (When cli is working) |
Closing as 3.0 Arm64 images are now available. |
@MichaelSimons |
@richlander @MichaelSimons It would be nice to start publishing arm64 docker images so more people can dogfood linux-arm64.
Is this is the place to do this? Or are there missing prerequisites in a supporting docker repo?
Is it too early for 2.2?
Worklist [added by MichaelSimons]
[Blocked on machine availability] CItracked with Build and test arm64 images as part of CI #792The text was updated successfully, but these errors were encountered: