Self-contained applications in Linux does not work

[AlbertoMonteiro]

Steps to reproduce

• mkdir hwapp
• cd hwapp
• dotnet new
• Modify project.json to match self-contained app

{
  "version": "1.0.0-*",
  "buildOptions": {
    "emitEntryPoint": true
  },
  "dependencies": {
    "Microsoft.NETCore.App": "1.0.0-rc2-3002702"
  },
  "frameworks": {
    "netcoreapp1.0": {}
  },
  "runtimes": {
    "ubuntu.14.04-x64: {}
  }
}

• dotnet restore
• dotnet publish -o out
• cd out
• hwapp

Expected behavior

Print Hello World!

Actual behavior

hwapp: command not found

Environment data

.NET Command Line Tools (1.0.0-preview1-002702)

Product Information:
 Version:     1.0.0-preview1-002702
 Commit Sha:  6cde21225e

Runtime Environment:
 OS Name:     ubuntu
 OS Version:  14.04
 OS Platform: Linux
 RID:         ubuntu.14.04-x64

[TheRealPiotrP]

@AlbertoMonteiro can you share the contents of the out directory?

You should also try running ./hwapp. @brthor suspects this is the issue here.

[brthor]

@AlbertoMonteiro I am not able to repro this when using ./hwapp

This is a linux shell requirement, and not something we control in the cli.

Please reopen if you still have issues.

[henrylle]

I have the same problem, but after exec ./hwapp I get this below error:
"Failed to load /home/ubuntu/teste-dotnet-rc2/libcoreclr.so, error: libunwind.so.8: cannot open shared object file: No such file or directory"

[AlbertoMonteiro]

@brthor It worked on the machined(ubuntu.14.04-x64) that I ran the publish command. I copied the output to another Linux distro(AWS Linux), and I got the same error pointed by @henrylle

Failed to load /home/ubuntu/teste-dotnet-rc2/libcoreclr.so, error: libunwind.so.8: cannot open shared object file: No such file or directory

[brthor]

@henrylle @AlbertoMonteiro Have you installed the dependencies of .NET Core?

You can use the debian package to bring them in with the installation of the cli or you need to install them manually.

You can see the list of packages in this dockerfile:
https://github.com/dotnet/cli/blob/rel/1.0.0/scripts/docker/ubuntu.14.04/Dockerfile#L20

[oshz]

@AlbertoMonteiro @henrylle The following link helped me resolve the library issue:

http://www.stevenmarkford.com/dotnet-core-failed-to-load-libcoreclr-so-libunwind-so-8-cannot-open-shared-object-file-on-ubuntu/

[dejfcz]

For anyone still running into this, try

apt-get install libunwind8

[Sword-Smith]

@dejfcz 's answer solved this problem for me.

[josemotta]

@dejfcz 's answer solved this problem for me too!

[code4clouds]

It solves the problem, but not the real issue. The application is not self-contained if it depends on a workaround. A self-contain application should run using just the kernel (i.e. Go with Docker scratch image).

[poma]

Or at least it should display a message that dependency is not installed

[wklm]

any updates on that? Is it possible to make a build truly self contained and include this dependency somehow?

[xczdbb]

On CoreOS, it's impossible to install libunwind because CoreOS doesn't have a package manager. A workaround is creating a container (Fedora/Ubuntu/etc) and run my .net core app inside it, but it's quite indirect. What's the correct way to deploy self-contained app on CoreOS?

[livarcocc]

This is not really a CLI issue at this point. When you are running a self-contained app or a portable app, you only use the runtime for that. I would suggest filling a separate issue about native dependencies on CoreOS over at dotnet/core-setup.

[wklm]

could we simply make the libunwind a part of the build in case it's not present on the os?

[olandese]

I was having the same problem on ubuntu 17.04, after installing libunwind8 with apt the .NET Core application was running successfully.
With a self contained application this should work without the need to install anything

[ghost]

Today we published and tried to run simple console app on fresh ubuntu WSL (16.04 LTS) & ubuntu azure (16.04 LTS). dotnetcore2
Tried linux-x64 & ubuntu.16.04-x64 runtime setups.

The same problem appeared. Installing libunwind8 did the job.

Is it going to be fixed at all? This way linux publish is not self contained. PERIOD.
We could install full dotnet runtime this way...

[dasMulli]

There is a document describing how to include 3rd party libraries for self-contained apps: https://github.com/dotnet/core/blob/master/Documentation/self-contained-linux-apps.md

Related: https://github.com/dotnet/coreclr/issues/5853
Which was closed with https://github.com/dotnet/coreclr/issues/5853#issuecomment-297864286

After the investigations and various experiments, it turned out that static linking is not feasible from various points of view and that a better approach to achieve portability over Linux distros is to change linking of some dependencies from build time to run time and to enable bundling of local copies of shared libraries. This has proven to work well, so I am closing this issue.

[WhatFreshHellIsThis]

Having the same issue "error: libunwind.so.8: cannot open shared object file: No such file or directory" This needs to be fixed.

[brthor]

When all else fails, pull the missing libraries from the microsoft docker image.
You can put them in the publish directory and distribute them with your app.

Quick example from my macbook:

Creating the project:

$ mkdir test && cd test
$ dotnet new console && dotnet publish -r linux-x64 --self-contained -o bin

If you run it on linux, expected result:

$ docker run -it -v $(pwd)/bin:/export ubuntu:latest /export/export
Failed to load ��', error: libunwind.so.8: cannot open shared object file: No such file or directory
Failed to bind to CoreCLR at '/export/libcoreclr.so'

Pull the libraries via docker (libunwind and libicu) and to your publish directory:

$ docker run -v $(pwd)/bin:/export microsoft/dotnet:2.0.0-sdk bash -c "cp /usr/lib/x86_64-linux-gnu/libicu* /export/"

$ docker run -v $(pwd)/bin:/export microsoft/dotnet:2.0.0-sdk bash -c "cp /usr/lib/x86_64-linux-gnu/libunwind* /export/"

Re-test:

$ docker run -it -v $(pwd)/bin:/export ubuntu:latest bash -c "LD_LIBRARY_PATH=/export /export/export"
Hello World

Success!

@WhatFreshHellIsThis @dasMulli @FDUdannychen

[lindexi]

@brthor I still cant run in my arm-32 for I cant install any lib.

[brthor]

@lindexi You're going to have to pull the libraries from one of the ARM 32 docker images. I suspect the path to the libraries will be different as well (not /usr/lib/x86_64-linux-gnu)

(See Here)[https://hub.docker.com/r/microsoft/dotnet/]

[brthor]

@livarcocc The experience surrounding this issue is awful, consider reopening it and fixing at least the experience if not the issue itself.

The average .NET Core user has no clue what libunwind is, and probably jumps back to building their service in Node.js or Ruby after they see an error like this.

This isn't an isolated incident either, this is a problem for EVERY self-contained linux app deployed to a machine without a portable framework installed. Self-contained apps are exactly the same as portable apps from a (single) deployment and usability perspective, for this reason.

There are several ways to solve this problem (without distributing the libraries yourself), I think the easiest of which is to print a command or set of commands that the user can copy/paste to run on their target machine (i.e. apt-get install libunwind8) whenever they do a self-contained deployment to a linux-x64 or child RID.

[lindexi]

@brthor Thx , but I cant install anything on my linux for it's a microcomputer that can only install when reinstalling the system. That I cant use docker or install libunwin.so.8 .

[adeel41]

For anyone still running into this, try

apt-get install libunwind8

Or if you running on CentOs then run
sudo yum install libunwind

[alexellis]

I just had this issue with .NET Core 2.2 on ARMHF and Docker. The fix was to add the libunwind apt package to the .NET core runtime container, I can't think why it wasn't already bundled into the runtime container image?

[zaneclaes]

5 years later, this is still happening with arm32v7 when creating a Docker image from the official dotnet5 Dockerfile. I am able to build that official Dockerfile on a RPi, but the resulting image will not run. However, I note that the official Dockerfile includes --self-contained false, making me wonder if dependencies were accidentally omitted. I added the libunwind8 dependency, but then ran into this issue instead.