slimtoolkit/slim

dotnet runtime lost

Open

#79 opened on May 24, 2019

View on GitHub
 (4 comments) (3 reactions) (0 assignees)Go (17,694 stars) (673 forks)batch import
enhancementfeaturehelp wanted

Description

I use a centos base image to build my dotnet runtime image.It becomes really slim(only 3.5M),but the dotnet runtime lost

Contributor guide

Tech stack
godocker
Domain
devopscloud
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Docker basics.NET runtime knowledgeGo programming
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Investigate the minification process for .NET container images. Look at how Slim detects and preserves runtime dependencies, possibly in the 'pkg/...' directory. Check if there is a specific handling for dotnet images or if it's a general file detection issue. Review comments on this issue for any clues. The fix may involve adding dotnet runtime files to the preserved list or adjusting the detection logic.