-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
error NETSDK1084: There is no application host available for the specified RuntimeIdentifier 'linux-x86' #31180
Comments
There are no official builds for Linux x86. https://github.com/dotnet/core-sdk cc: @richlander |
The docs at https://docs.microsoft.com/en-us/dotnet/core/rid-catalog say:
The runtime.json file does have a Why is there an x86 build for Windows but not Linux? I've got a few VPSes with very limited RAM (128 MB) which I'd like to run .NET Core apps on. With such a small amount of RAM there's not really any benefits of 64-bit over 32-bit. |
I'm trying to cross-build the runtime using an Ubuntu 18.04 x86-64 for a linux-x86 system. I do receive also this error. |
Referring to this. How? what parameters to the build scripts? Following the README took me nowhere |
There are many RIDs which are present in the graph which are not built by Microsoft. Some are built by the community or other parties. The list of RIDs which the SDK supports for self-contained apps is stored here: https://github.com/dotnet/installer/blob/8b9782a074c51ef9f8b8b0608870c23ed77df7f5/src/redist/targets/GenerateBundledVersions.targets#L181-L192 @dsplaisted might be able to comment if there's a good place where this is documented. Moving this to area-Infrastructure as it has become a question of building the product. |
Tagging subscribers to this area: @dotnet/runtime-infrastructure Issue DetailsTrying to publish a project for
Can
|
I would imagine that you'd want to build dotnet/runtime for linux-x86 release, the output you'd be interested in is the runtime-pack. Then you could tell the SDK to use this when publishing your self-contained app. Given we don't officially support this, there is no guarantee it would work. It looks like #7335 tracks an effort to build the product for x86. |
Considering you get this very error when you cross-compile an x86 build I don't think you can use this approach to produce a runtime-pack (see last note in the issue you linked, and I just verified it still is regressed and produces this error). Note that cross compiling x86 on an x64 host is the only way to produce x86 binaries, since you cannot compile the dotnet runtime on an x86 host (the build process needs more memory than an x86 host can manage) I've managed to cross compile in the past with an earlier version, before the cross compilation regressed, but even then I never managed to convince the SDK to actually use the produced artifacts; and building the SDK itself for x86 is impossible (for me), the build scripts are too poorly managed/documented. |
Having this same issue when trying to publish an application, but instead to a ARM target with softfpu, requiring linux-armel, doing this with the below command on .NET 6.0.101 on VS2022. Is there any guide on how to build the SDK and inform dotnet of its existence so the below works? |
as you noted Microsoft does not provide official builds for Linux x86, so how did you get that SDK/runtime? did you compile it yourself? are you trying to cross-compile on a 64 bit machine? this is known to not work since there are no official builds of the platform specific packages for x86 on nuget, you'd have to make your own maybe add some information about what you're doing, but the most likely response will be "you are on your own, this can be made working but is not officially supported" PS: I got compiling the runtime to work years ago, see the linked issue from earlier, but never got the SDK to build for x86 out of the box, so as far as I can tell its only possible if you put lots of effort into it to customize/fix the build scripts [edit] it looks like someone on the other issue got the SDK to build for earlier versions of .NET Core after all, so thats probably what you are looking for if you're trying to get this working yourself |
Have same problem with missed RID on 9.0 (upstream branch): |
Trying to publish a project for
linux-x86
fails:linux-x64
works fine though.Can
--self-contained
not be used for 32-bit Linux builds?The text was updated successfully, but these errors were encountered: