-
Notifications
You must be signed in to change notification settings - Fork 4.9k
CentOS, RHEL: aspnetcore-runtime RPM doesn't install the ASP.NET Core Runtime #3886
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
Comments
I'm having this problem as well - looks like i should be getting the download for aspnetcore-runtime-2.2.8-x64.rpm, but there's a reference to aspnetcore-runtime-2.2.8-rh.rhel.7-x64.rpm instead (which doesn't exist). |
Yeah, there are two cases here:
Which one you hit depends on which distro you're on and whether you're installing 2.1/2.2/3.0. Once the |
The same here. error: The same error for older 2.2 versions The missing file is not here: Thanks |
I think it's worth mentioning that the workaround for the 404 also works for this issue:
|
Thanks, I missed the workaround when I ran across that one, that got me working! |
Just ran into this today on a couple machines. Your work around worked, thanks! |
@leecow is this still an issue? |
You need run command "$ sudo yum makecache", for example: |
Still an issue on RHEL8.3, aspnetcore-runtime-2.1 installs into /usr/share/dotnet/shared/Microsoft.AspNetCore.All but dotnet lives in /usr/lib64/dotnet/shared/. Creating the symlinks makes it go brrr ln -s /usr/share/dotnet/shared/Microsoft.AspNetCore.All/ /usr/lib64/dotnet/shared/Microsoft.AspNetCore.All |
Hey @j-hudecek! Thanks for pointing this out. In case you are not aware, there's a workaround for this documented here. The TLDR is to publish applications like this:
Installing the packages and symlinking might also work, but it's more brittle than using this The issues is fixed in later releases (3.1 and 5.0 as of this writing). |
Copy of #3863, where the specific repro was resolved, but it seems it still happens on other distros and versions.
I believe this may still happen on some distros in any of 2.1, 2.2, or 3.0.
/cc @leecow
The text was updated successfully, but these errors were encountered: