-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Alpine Linux (for Docker images) #226
Comments
See this issue: https://github.com/dotnet/coreclr/issues/917 |
Hm, seems like dotnet/coreclr#917 covers the work of porting to Alpine Linux. @markrendle you ok if we close this issue? |
Closing this issue due to lack of response. |
Hello @markrendle I have this issue while using this lib
|
@mo-saeed it would probably be better to open a new issue given this one was closed due to the lack of response and it's almost 5 years old. |
Support for Alpine Linux has been mentioned in the past on various repositories. It's desirable because the Docker image for Alpine is under 5MB in size, compared to over 100MB for Debian 8, which is the current base for the
dotnet
images. Docker are looking to migrate all their official library images to Alpine.The blocker for .NET Core has been the availability of the core dependencies on Alpine, of which the last outstanding one was LTTng, which is now in the APK testing repository for Alpine 3.5.
I'm not an expert on building .NET Core, CLI, etc, but if anybody fancies having a go at creating an Alpine build, it should be possible.
Looking at the Linux build instructions for CoreCLR, all the APT packages mentioned are available now, at least in Alpine's edge/testing repository, if not in edge/main:
uuid.h
file lives)And here's a list of the deps from the
dotnet
image with their Alpine equivalents.Right, this is where somebody points out that the only reason these dependencies have made it into Alpine is that a .NET Core team member ported them all, for precisely this reason, and I've wasted the time spent on this issue. 😞
The text was updated successfully, but these errors were encountered: