Cannot install .NET Core 2.0 on Amazon Linux AMI #930

goforgold · 2017-09-02T12:39:38Z

I am trying to update from .NET Core 2.0 Preview 2 Final to 2.0 Final Release on the Amazon EC2 instance due to some dependency issue.

When I run install command sudo yum install dotnet-sdk-2.0.0 it produces following error.

Error: Package: dotnet-runtime-2.0.0-2.0.0-1.x86_64 (packages-microsoft-com-prod)
           Requires: openssl-libs

And, when I try to install openssl-libs using package manager with command yum install openssl-libs, it says No package openssl-libs available.

I've checked package repository and didn't found any package with name openssl-libs there. However, openssl is installed already in the machine, I confirmed that by running openssl version command. The version is 1.0.1k-fips 8 Jan 2015.

Please suggest how to resolve this dependency.

The text was updated successfully, but these errors were encountered:

heathhey · 2017-09-04T16:26:48Z

You might have better luck following the instructions here:

https://github.com/dotnet/core/blob/0b1a1631593d6d379fbdfe2b23597a5c25ea4fc9/Documentation/build-and-install-rhel6-prerequisites.md

Amazon Linux already has a later version of curl, so you might need libcurl-devel installed as well.

goforgold · 2017-09-11T03:46:56Z

I managed to install .NET Core 2.0 using the source code as instructed here.

I didn't find any complexity in that way. It hardly took 10 minutes to get everything setup.

hchungi · 2017-09-11T05:22:32Z

I was almost desperate.
I tries many ways, none of them can work for me.

Afterwards, I download the .NET Core 2.0 runtime directly with following link:

https://download.microsoft.com/download/5/F/0/5F0362BD-7D0A-4A9D-9BF9-022C6B15B04D/dotnet-runtime-2.0.0-linux-x64.tar.gz

And, use the old fashion way like installing .net core 1.1 with commands:

sudo mkdir -p /opt/dotnet && sudo tar zxf dotnet-runtime-2.0.0-linux-x64.tar.gz -C /opt/dotnet
sudo ln -s /opt/dotnet/dotnet /usr/local/bin

It worked. Very simple like you used to do.

zl4bv · 2017-09-28T04:19:51Z

Does not work with Amazon Linux when following these instructions.

[ec2-user@ip-xx-xx-xx-xx ~]$ sudo yum install dotnet-sdk-2.0.0
Loaded plugins: priorities, update-motd, upgrade-helper
Resolving Dependencies
--> Running transaction check
---> Package dotnet-sdk-2.0.0.x86_64 0:2.0.0-1 will be installed
--> Processing Dependency: dotnet-runtime-2.0.0 >= 2.0.0 for package: dotnet-sdk-2.0.0-2.0.0-1.x86_64
--> Processing Dependency: aspnetcore-store-2.0.0 >= 2.0.0 for package: dotnet-sdk-2.0.0-2.0.0-1.x86_64
--> Running transaction check
---> Package aspnetcore-store-2.0.0.x86_64 0:2.0.0-1 will be installed
---> Package dotnet-runtime-2.0.0.x86_64 0:2.0.0-1 will be installed
--> Processing Dependency: openssl-libs for package: dotnet-runtime-2.0.0-2.0.0-1.x86_64
--> Processing Dependency: dotnet-hostfxr-2.0.0 for package: dotnet-runtime-2.0.0-2.0.0-1.x86_64
--> Running transaction check
---> Package dotnet-hostfxr-2.0.0.x86_64 0:2.0.0-1 will be installed
--> Processing Dependency: dotnet-host >= 2.0.0 for package: dotnet-hostfxr-2.0.0-2.0.0-1.x86_64
---> Package dotnet-runtime-2.0.0.x86_64 0:2.0.0-1 will be installed
--> Processing Dependency: openssl-libs for package: dotnet-runtime-2.0.0-2.0.0-1.x86_64
--> Running transaction check
---> Package dotnet-host.x86_64 0:2.0.0-1 will be installed
---> Package dotnet-runtime-2.0.0.x86_64 0:2.0.0-1 will be installed
--> Processing Dependency: openssl-libs for package: dotnet-runtime-2.0.0-2.0.0-1.x86_64
--> Finished Dependency Resolution
Error: Package: dotnet-runtime-2.0.0-2.0.0-1.x86_64 (packages-microsoft-com-prod)
           Requires: openssl-libs
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

wfurt · 2017-09-28T04:34:29Z

If you already have openssl you can try to run yum with --skip-broken (as the message suggests)
All what dotnet needs is to find dynamic libraries from openssl. (and libcurl)

wfurt · 2017-09-28T04:39:08Z

BTW AMI Linux is NOT one of the supported and test platforms. There should be no surprise that there are some bumps. This is one reason for publishing the tar file so you do not need to fight package dependencies.

h3smith · 2017-09-28T04:59:35Z

If you want to use AWS, drop it in Docker and use ECS.

Paschoali · 2017-10-06T16:00:33Z

Like hchungi said, I just did:

Download .NET Core 2.0.0 runtime libraries (always check if URL is right, maybe it can be changed):
wget https://download.microsoft.com/download/5/F/0/5F0362BD-7D0A-4A9D-9BF9-022C6B15B04D/dotnet-runtime-2.0.0-linux-x64.tar.gz

Create folder to .NET Core and extract your tar.gz:

mkdir -p $HOME/dotnet && tar zxf dotnet-runtime-2.0.0-linux-x64.tar.gz -C $HOME/dotnet

Finally, export dotnet to globally variable:
export PATH=$PATH:$HOME/dotnet

Just it :)

goforgold · 2017-10-06T16:03:21Z

This is exactly how I did this around a month ago. Thank you very much to confirm the solution.

…

On 06-Oct-2017 21:31, "Bruno Paschoali Regis" ***@***.***> wrote: Like hchungi said, I just did: Download .NET Core 2.0.0 runtime libraries (always check if URL is right, maybe it can be changed): wget https://download.microsoft.com/download/5/F/0/5F0362BD- 7D0A-4A9D-9BF9-022C6B15B04D/dotnet-runtime-2.0.0-linux-x64.tar.gz Create folder to .NET Core and extract your tar.gz: mkdir -p $HOME/dotnet && tar zxf dotnet-runtime-2.0.0-linux-x64.tar.gz -C $HOME/dotnet Finally, export dotnet to globally variable: export PATH=$PATH:$HOME/dotnet Just it :) — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#930 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABpaVdhf_5I669PIpGH-5LqGA8H83mSCks5spk7JgaJpZM4PK47F> .

Petermarcu · 2017-10-06T16:24:58Z

Sounds like people have found a good solution. I'm going to close this out now.

goforgold · 2017-10-06T16:27:14Z

But I wish if I could install this simply using package manager on AWS AMI.

…

On 06-Oct-2017 21:55, "Peter Marcu" ***@***.***> wrote: Sounds like people have found a good solution. I'm going to close this out now. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#930 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABpaVZb1hBFEZ3GcMuot2i26cZiFmhQiks5splSFgaJpZM4PK47F> .

omajid · 2017-10-06T16:34:13Z

Any chance you could try a distribution other than Amazon Linux? The .NET Core project publishes packages for several distributions (such as CentOS, Debian, Ubuntu) and several other distributions are now starting to carry .NET Core too (such as Arch, CentOS, Fedora, RHEL). I dont know if we have a way to contribute packages to Amazon Linux directly.

Petermarcu · 2017-10-06T16:34:50Z

Yes, I've been told the Centos one works: https://www.microsoft.com/net/core#linuxcentos

Petermarcu · 2017-10-06T16:35:42Z

I would assume that someone needs to work with AWS to get .NET Core into their package feed.

goforgold · 2017-10-06T16:37:01Z

Yes, I thought about that and researched on that too. But, many resources suggests that AWS AMI perofoms best in AWS infrastructures.

…

On 06-Oct-2017 22:05, "Omair Majid" ***@***.***> wrote: Any chance you could try a distribution other than Amazon Linux? The .NET Core project publishes packages for several distributions (such as CentOS, Debian, Ubuntu) and several other distributions are now starting to carry .NET Core too (such as Arch, CentOS, Fedora, RHEL). I dont know if we have a way to contribute packages to Amazon Linux directly. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#930 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABpaVbvaBiUBObEdMh3psUzFHrdJJFd2ks5spla3gaJpZM4PK47F> .

robyle · 2017-10-11T09:42:54Z

I use the Aliyun ECS,The OS version is Centos 6.8. I also met this problem.The Information like this:
[root@iZwz9bh8rvZ ~]# sudo yum install dotnet-sdk-2.0.0
Loaded plugins: fastestmirror
Setting up Install Process
Loading mirror speeds from cached hostfile
Resolving Dependencies
--> Running transaction check
---> Package dotnet-sdk-2.0.0.x86_64 0:2.0.0-1 will be installed
--> Processing Dependency: dotnet-runtime-2.0.0 >= 2.0.0 for package: dotnet-sdk-2.0.0-2.0.0-1.x86_64
--> Processing Dependency: aspnetcore-store-2.0.0 >= 2.0.0 for package: dotnet-sdk-2.0.0-2.0.0-1.x86_64
--> Running transaction check
---> Package aspnetcore-store-2.0.0.x86_64 0:2.0.0-1 will be installed
---> Package dotnet-runtime-2.0.0.x86_64 0:2.0.0-1 will be installed
--> Processing Dependency: openssl-libs for package: dotnet-runtime-2.0.0-2.0.0-1.x86_64
--> Processing Dependency: dotnet-hostfxr-2.0.0 for package: dotnet-runtime-2.0.0-2.0.0-1.x86_64
--> Running transaction check
---> Package dotnet-hostfxr-2.0.0.x86_64 0:2.0.0-1 will be installed
--> Processing Dependency: dotnet-host >= 2.0.0 for package: dotnet-hostfxr-2.0.0-2.0.0-1.x86_64
---> Package dotnet-runtime-2.0.0.x86_64 0:2.0.0-1 will be installed
--> Processing Dependency: openssl-libs for package: dotnet-runtime-2.0.0-2.0.0-1.x86_64
--> Running transaction check
---> Package dotnet-host.x86_64 0:2.0.0-1 will be installed
---> Package dotnet-runtime-2.0.0.x86_64 0:2.0.0-1 will be installed
--> Processing Dependency: openssl-libs for package: dotnet-runtime-2.0.0-2.0.0-1.x86_64
--> Finished Dependency Resolution
Error: Package: dotnet-runtime-2.0.0-2.0.0-1.x86_64 (packages-microsoft-com-prod)
Requires: openssl-libs
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest

Paschoali · 2017-10-11T13:42:58Z

Aliyun ECS? Whatever, did you read the comments? We suggested some solutions. Sure that of them will help you.

heathhey · 2017-10-11T17:03:19Z

Is there a SRPM for the dotnet-runtime package? Or is there a spec file in the repo somewhere? I couldn't find one.

omajid · 2017-10-11T17:46:03Z

Is there a SRPM for the dotnet-runtime package? Or is there a spec file in the repo somewhere?

We use fpm to produce RPMs (and debs) instead of using rpmbuild. There are no SPRMs or spec files because of that.

The configuration for -runtime and -host RPMs is available here: https://github.com/dotnet/core-setup/tree/master/src/pkg/packaging/rpm

Here is the source that reads that config files above to build command line for fpm: https://github.com/dotnet/core-setup/blob/master/tools-local/tasks/BuildFPMToolPreReqs.cs

ozyman42 · 2017-11-30T11:56:30Z

The old links may not work so go here https://github.com/dotnet/core/blob/master/release-notes/download-archives/2.0.0-download.md and use the SDK binary link for the latest tar.gz file.

gtechx · 2018-04-08T07:48:29Z

I am a client programmer.
I do not like to install any dependency myself on linux.
some problems are too difficulty to solve.
see golang.

ddobric · 2018-05-23T09:34:46Z

Unfortunately I didn't make this working. Using hortonworks sandbox withCentOS.
Error as already mentioned above:

Error: Package: dotnet-runtime-2.0.6-2.0.6-1.x86_64 (packages-microsoft-com-prod )
Requires: openssl-libs
Error: Package: dotnet-runtime-deps-2.1.0-rc1-2.1.0_rc1-1.x86_64 (packages-micro soft-com-prod)

jchannon · 2018-07-11T10:53:12Z

Installing Net Core 2.1 on Amazon Linux still seems to be an issue :(

wfurt · 2018-07-11T14:50:11Z

What base OS do you use and what .Net package? Did you check that everything works using tar distro? I'm trying to figure out if this is pure packaging issue or if there are really missing dependencies.

jchannon · 2018-07-11T14:54:46Z

I did sudo rpm -Uvh https://packages.microsoft.com/config/rhel/7/packages-microsoft-prod.rpm and yum update and yum install dotnet-sdk-2.1

Output is below:

amazon-linux-ami: Resolving Dependencies
    amazon-linux-ami: --> Running transaction check
    amazon-linux-ami: ---> Package dotnet-sdk-2.1.x86_64 0:2.1.301-1 will be installed
    amazon-linux-ami: --> Processing Dependency: dotnet-runtime-2.1 >= 2.1.1 for package: dotnet-sdk-2.1-2.1.301-1.x86_64
    amazon-linux-ami: --> Processing Dependency: aspnetcore-runtime-2.1 >= 2.1.1 for package: dotnet-sdk-2.1-2.1.301-1.x86_64
    amazon-linux-ami: --> Running transaction check
    amazon-linux-ami: ---> Package aspnetcore-runtime-2.1.x86_64 0:2.1.2-1 will be installed
    amazon-linux-ami: ---> Package dotnet-runtime-2.1.x86_64 0:2.1.2-1 will be installed
    amazon-linux-ami: --> Processing Dependency: dotnet-hostfxr-2.1 >= 2.1.2 for package: dotnet-runtime-2.1-2.1.2-1.x86_64
    amazon-linux-ami: --> Processing Dependency: dotnet-runtime-deps-2.1 >= 2.1.2 for package: dotnet-runtime-2.1-2.1.2-1.x86_64
    amazon-linux-ami: --> Running transaction check
    amazon-linux-ami: ---> Package dotnet-hostfxr-2.1.x86_64 0:2.1.2-1 will be installed
    amazon-linux-ami: --> Processing Dependency: dotnet-host >= 2.1.2 for package: dotnet-hostfxr-2.1-2.1.2-1.x86_64
    amazon-linux-ami: ---> Package dotnet-runtime-2.1.x86_64 0:2.1.2-1 will be installed
    amazon-linux-ami: --> Processing Dependency: dotnet-runtime-deps-2.1 >= 2.1.2 for package: dotnet-runtime-2.1-2.1.2-1.x86_64
    amazon-linux-ami: --> Running transaction check
    amazon-linux-ami: ---> Package dotnet-host.x86_64 0:2.1.2-1 will be installed
    amazon-linux-ami: ---> Package dotnet-runtime-2.1.x86_64 0:2.1.2-1 will be installed
    amazon-linux-ami: --> Processing Dependency: dotnet-runtime-deps-2.1 >= 2.1.2 for package: dotnet-runtime-2.1-2.1.2-1.x86_64
    amazon-linux-ami: --> Finished Dependency Resolution
    amazon-linux-ami:  You could try using --skip-broken to work around the problem
    amazon-linux-ami: Error: Package: dotnet-runtime-2.1-2.1.2-1.x86_64 (packages-microsoft-com-prod)
    amazon-linux-ami:            Requires: dotnet-runtime-deps-2.1 >= 2.1.2
    amazon-linux-ami:            Available: dotnet-runtime-deps-2.1-2.1.0-1.x86_64 (packages-microsoft-com-prod)
    amazon-linux-ami:                dotnet-runtime-deps-2.1 = 2.1.0-1
    amazon-linux-ami:            Available: dotnet-runtime-deps-2.1-2.1.1-1.x86_64 (packages-microsoft-com-prod)
    amazon-linux-ami:                dotnet-runtime-deps-2.1 = 2.1.1-1
    amazon-linux-ami:  You could try running: rpm -Va --nofiles --nodigest

wfurt · 2018-07-11T16:02:45Z

cc: @tmds. seems like it cannot find dotnet-runtime-deps-2.1 -2.1.2

tmds · 2018-07-11T16:37:39Z

@wfurt, @jchannon is installing from Microsoft feed. Are those packages missing?

jchannon · 2018-07-11T16:45:55Z

just followed the instructions here https://www.microsoft.com/net/download/linux-package-manager/centos/sdk-current

leecow · 2018-07-11T17:09:10Z

Looks like the updated runtime-deps and sdk didn't make the upload. Checking into this now.

leecow · 2018-07-11T17:21:02Z

Alrighty, sorry about that. Give it another whirl now.

jchannon · 2018-07-11T19:33:08Z

A bit better but now says runtime needs openssl-libs. I added yum install openssl-libs but it says "No package openssl-libs available."

…

On 11 July 2018 at 18:21, Lee Coward ***@***.***> wrote: Alrighty, sorry about that. Give it another whirl now. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#930 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAGaphtEXiz4S0ulpYRPsNe1S-pIqkIcks5uFjQhgaJpZM4PK47F> .

wfurt · 2018-07-11T20:15:49Z

That goes back to original issue. AMI Linux names packages different than RedHat. Now, assuming you have correct openssl 1.0.x installed you can try following trick:

openssl-libs-ami.spec.txt

Download attached spec file.

rpmbuild --bb openssl-libs-ami.spec.txt
That should produce empty openssl-libs in /root/rpmbuild/RPMS/
(use find if not there as the location may wary)
rpm -i openssl-libs-1.0.0-0.x86_64.rpm

and try the install again.
Good luck. AMI linux is not tested so .net may or may not work properly.
The instructions should help you to at least try.

sjwoodard · 2018-10-15T21:59:12Z

The @wfurt solution worked for me, just run sudo yum install rpm-build to get started.

juancrl · 2018-12-10T10:59:04Z

Perfect also in my case. The folder was different, as stated :

sudo yum install rpm-build
wget https://github.com/dotnet/core/files/2186067/openssl-libs-ami.spec.txt
rpmbuild --bb openssl-libs-ami.spec.txt
sudo rpm -i /root/rpmbuild/RPMS/x86_64/openssl-libs-1.0.0-0.x86_64.rpm
sudo yum install -y powershell

ptdel · 2019-03-06T17:48:30Z

Provides: openssl-libs = 1.0.0-0 openssl-libs(x86-64) = 1.0.0-0
Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1
Checking for unpackaged file(s): /usr/lib/rpm/check-files /usr/src/rpm/BUILDROOT/openssl-libs-1.0.0-0.x86_64
Wrote: /usr/src/rpm/RPMS/x86_64/openssl-libs-1.0.0-0.x86_64.rpm
Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.13DnAm

for whatever reason this chose today to start hanging forever during deployments. I don't see an actual %clean step in the rpm spec.

darshit95 · 2019-10-04T21:24:22Z

Folks who are trying to install azure powershell and have ended up here can use @juancrl mentioned solution, it surely works !
sudo yum install rpm-build
wget https://github.com/dotnet/core/files/2186067/openssl-libs-ami.spec.txt
rpmbuild --bb openssl-libs-ami.spec.txt
sudo rpm -i /root/rpmbuild/RPMS/x86_64/openssl-libs-1.0.0-0.x86_64.rpm
sudo yum install -y powershell

vvaezian · 2020-10-08T22:15:33Z

For me the path of created openssl-libs was different. So I had to find it first (as suggested by wfurt)

wget https://github.com/dotnet/core/files/2186067/openssl-libs-ami.spec.txt
rpmbuild --bb openssl-libs-ami.spec.txt
sudo find / -iname RPMS  # output: /usr/src/rpm/RPMS
sudo rpm -i /usr/src/rpm/RPMS/x86_64/openssl-libs-1.0.0-0.x86_64.rpm
sudo yum install -y powershell

goforgold mentioned this issue Sep 2, 2017

Where from I can download Preview 2 Final Version #929

Closed

Petermarcu closed this as completed Oct 6, 2017

daxian-dbw mentioned this issue Oct 10, 2017

New RPM package doesn't work for AmazonLinux PowerShell/PowerShell#5027

Closed

SteveL-MSFT mentioned this issue Oct 24, 2018

Dependency Error While Installing PowerShell on AMI Linux PowerShell/PowerShell#6398

Closed

ptdel mentioned this issue Mar 11, 2019

dotnet amazon linux builds broken #2423

Closed

hellowahab mentioned this issue Oct 10, 2019

Cannot install .NET Core 3.0 on Amazon Linux AMI #3583

Closed

kessplas mentioned this issue Aug 9, 2022

Add dotnet install and add C# code for workshop examples, update instructions to include C# aws-samples/busy-engineers-document-bucket#268

Merged

Cannot install .NET Core 2.0 on Amazon Linux AMI #930

Cannot install .NET Core 2.0 on Amazon Linux AMI #930

Comments

goforgold commented Sep 2, 2017

heathhey commented Sep 4, 2017

goforgold commented Sep 11, 2017

hchungi commented Sep 11, 2017

zl4bv commented Sep 28, 2017

wfurt commented Sep 28, 2017

wfurt commented Sep 28, 2017

h3smith commented Sep 28, 2017

Paschoali commented Oct 6, 2017

goforgold commented Oct 6, 2017 via email

Petermarcu commented Oct 6, 2017

goforgold commented Oct 6, 2017 via email

omajid commented Oct 6, 2017

Petermarcu commented Oct 6, 2017

Petermarcu commented Oct 6, 2017

goforgold commented Oct 6, 2017 via email

robyle commented Oct 11, 2017

Paschoali commented Oct 11, 2017

heathhey commented Oct 11, 2017

omajid commented Oct 11, 2017

ozyman42 commented Nov 30, 2017 • edited Loading

gtechx commented Apr 8, 2018

ddobric commented May 23, 2018

jchannon commented Jul 11, 2018

wfurt commented Jul 11, 2018

jchannon commented Jul 11, 2018

wfurt commented Jul 11, 2018

tmds commented Jul 11, 2018

jchannon commented Jul 11, 2018 • edited Loading

leecow commented Jul 11, 2018

leecow commented Jul 11, 2018

jchannon commented Jul 11, 2018 via email

wfurt commented Jul 11, 2018

sjwoodard commented Oct 15, 2018

juancrl commented Dec 10, 2018

ptdel commented Mar 6, 2019 • edited Loading

darshit95 commented Oct 4, 2019

vvaezian commented Oct 8, 2020

ozyman42 commented Nov 30, 2017 •

edited

Loading

jchannon commented Jul 11, 2018 •

edited

Loading

ptdel commented Mar 6, 2019 •

edited

Loading