Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

dotnet core RHEL-x64 publish output doesn't work with RHEL 6.x versions

See original GitHub issue

When we build and publish self contained application with runtime identifier rhel-x64 and tried to use it on RHEL 6.x platform, we get following error

“dlopen failed to open the libcoreclr.so with error /lib64/libc.so.6: version `GLIBC_2.14’ not found”

If we publish with rhel.6-x64 identifier and use these published binaries, then it works correctly on RHEL 6.x platform.

We are using dotnet core SDK 2.1.3 RC1 build with runtime version 2.0.4 (which supports RHEL 6.x platform as per below link) https://github.com/dotnet/core/blob/master/Documentation/build-and-install-rhel6-prerequisites.md

We expect binaries published with portable runtime identifier to work for all versions of that specific platform.

Issue Analytics

State:
Created 5 years ago
Comments:5 (4 by maintainers)

Top GitHub Comments

2reactions

omajidcommented, May 31, 2018

As I understand it, the cli artifacts for the rhel-x64 RID are built on RHEL 7 (or similar) and require features in newer glibc. The cli artifacts for the rhel.6-x64 RID are built on RHEL 6 (or similar) and do not require the newer features from glibc. Something built on a newer glibc is just not going to work on an older glibc.

The flips side would be to build everything on RHEL 6 and use that as the base. Perhaps CoreCLR experts can explain why they didn’t do it that way - I am sure there are issues.

0reactions

AmeetShindecommented, Jun 3, 2018

@janvorli Thanks for the detailed explanation. I am assuming that publish output bianries of our application with RID rhel.6-x64 wouldn’t work with RHEL 7.x, can you please confirm the same?