Closed sentient-glare closed 1 year ago
I believe we will need to build separate binaries for alpine/musl
Gotcha - using Alpine isn't a requirement for me but I got similar results with Debian and Ubuntu
oops. I will look into it.
@sentient-glare I tried to reproduce the crash on glibc based base image and could not reproduce
Here is what I tried: https://github.com/pyroscope-io/pyroscope/blob/fix/crash_dotnet_example/examples/dotnet/web-new/Dockerfile
I wonder what is the difference with your setup on debian base image. Is there any chance you could share a stacktrace of segmentation fault? or even better a coredump? or even better full self-contained example crashing(not alpine)?
Btw, what is your host OS and architecture?
Sorry for the wait on this. I tried out a Dockerfile similar to yours and it worked fine for me, I think I didn't track my local testing all that well and it was using Alpine images that was the issue all along and/or was doing some funky stuff with the libraries 😢 the debian images all work for me now. thanks for the help!
Following the instructions for the dotnet beta integration. I am trying to profile an ASPNET application with Pyroscope.
Dockerfile below - this is largely copied from a Microsoft example. When I build and run this, the container exits with a
139
code (seg fault).Things I've tried:
0.7.2
to0.7.0
libc6-compat
library instead ofgcompat