Skip to content
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

Documentation: Install on CentOS 6 #13299

Closed
savornicesei opened this issue Aug 22, 2019 · 8 comments
Closed

Documentation: Install on CentOS 6 #13299

savornicesei opened this issue Aug 22, 2019 · 8 comments
Labels
area-Infrastructure-coreclr backlog-cleanup-candidate An inactive issue that has been marked for automated closure. no-recent-activity question Answer questions and provide assistance, not an issue with source code or documentation.

Comments

@savornicesei
Copy link

Hi all,

This is related to issue #6519 and this documentation page.

On a fresh CentOS 6.10, updating curl library breaks yum (it complains about not beeing able to read /etc/yum.conf file).
Setting LD_LIBRARY_PATH back to /usr/lib fixes yum.
But still, yum install fails because of the openssl-libs dependency that is not available on CentOS 6.
The only solution to bypass the yum dependencies check is to install the dotnet packages using rpm.

I have tried the following dotnet repositories:

If it's possible to install dotnet from source on CentOS 6 then the documentation needs to be updated. But as it is now - it's not helping getting dotnet 2.x on CentOS 6.

Thank you,
Simo

@janvorli
Copy link
Member

@savornicesei let me try to verify the steps from the doc (https://github.com/dotnet/core/blob/master/Documentation/build-and-install-rhel6-prerequisites.md). At the time I have written it, they were working on fresh CentOS 6 install. So maybe something has changed.
Btw, the LD_LIBRARY_PATH should not be set to /usr/local/lib permanently, only for running the .NET Core applications. The simplest way is to put LD_LIBRARY_PATH=/usr/local/lib at the beginning of the command line that starts the .NET core app. Then the curl built from sources cannot interfere with yum in any way.

@savornicesei
Copy link
Author

@janvorli I have a VM with CentOS 6 that I can easily rollback to a clean system. Let me know if I can help in any way.

@janvorli
Copy link
Member

@savornicesei I have just verified the steps provided in the document on a freshly created CentOS 6.10 docker container, which should be the most minimal version of CentOS 6.10.
I have found three minor issues:

  • the dependency list contains krb5 package, which should be krb5-libs instead
  • the command to build CURL from sources was missing backslash at the end of the line with --prefix=$PWD/install/usr/local.
  • The export LD_LIBRARY_PATH=/usr/local/lib is not correct, you should never set the LD_LIBRARY_PATH this way as it is set for all the commands that you execute after that. It really needs to be set only for running .NET core apps (or the dotnet tool itself). Otherwise it breaks other apps like the yum.

But other than that, everything worked as expected. I've downloaded .NET Core SDK 2.2 after installing all the stuff and I was able to build and run the hello world app.

@janvorli
Copy link
Member

Btw, I've downloaded the 2.2 sdk tarball from https://dotnet.microsoft.com/download/thank-you/dotnet-sdk-2.2.401-linux-rhel-6-x64-binaries

@savornicesei
Copy link
Author

Hi @janvorli
Are you referring to this docker container?
So it actually needs to be built from source not installed through yum. That makes more sense.

@janvorli
Copy link
Member

No, I meant the vanilla centos:6.10 image. To make it clear, I've ran the following command to create and run the container in which I've then made all the steps described in the doc.

docker run -it centos:6.10 /bin/bash

@msftgits msftgits transferred this issue from dotnet/coreclr Jan 31, 2020
@msftgits msftgits added this to the Future milestone Jan 31, 2020
Copy link
Contributor

Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.

This process is part of our issue cleanup automation.

@dotnet-policy-service dotnet-policy-service bot added backlog-cleanup-candidate An inactive issue that has been marked for automated closure. no-recent-activity labels May 12, 2024
Copy link
Contributor

This issue will now be closed since it had been marked no-recent-activity but received no further activity in the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will be locked if it remains inactive for another 30 days.

@dotnet-policy-service dotnet-policy-service bot removed this from the Future milestone May 26, 2024
Infrastructure Backlog automation moved this from Future to Closed May 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-Infrastructure-coreclr backlog-cleanup-candidate An inactive issue that has been marked for automated closure. no-recent-activity question Answer questions and provide assistance, not an issue with source code or documentation.
Projects
Status: Done
Development

No branches or pull requests

3 participants