Closed RussKeldorph closed 6 years ago
@brianrob
@vancem
FYI, I am looking into this. It appears that the docker images are possibly using a much newer kernel than the default installation of Debian Jessie. The images also appear to strip a good number of the package sources.
I am working on setting up a machine with Debian Jessie so I can see what's different.
It looks like the default Debian Jessie installation uses kernel 3.16, which has a corresponding perf package. @MichaelSimons, do you know where the 4.13 kernel in our debian jessie docker images comes from? I can't find a corresponding linux-tools-4.13 or linux-perf-4.13 package that can be installed with the 4.13 kernel on either debian jessie or debian stretch.
@MichaelSimons can you comment on the question above? Thanks.
Fixed via #78.
The problem is still there as uname
returns Linux
from the dotnet docker images, and the script is not expecting this value.
Just merged #79 that will hopefully help. I tested on stretch and it looks like you're running on Jessie. The result of uname should not matter for Debian because we'll also check /etc/os-release.
Please try the latest version of perfcollect and see if that helps.
From @sebastienros on April 20, 2018 0:3
In a
microsoft/dotnet:2.0-sdk-jessie
image, runningperfcollect install
errors with an unsupported linux distribution.uname
returnsLinux
which isn't handled.I tried to install manually based on
Debian
instructions, however after installingzip
andlinux-tools
I still get aCopied from original issue: dotnet/coreclr#17686