slimtoolkit / slimtoolkit/slim
slim image size is different each time from same fat image and use same cmd line
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.4k
- Forks
- 840
- PR merge metrics
- No merged PRs in 30d
Description
Expected Behavior
generated slim image have stable size output
Actual Behavior
differenct each time
Steps to Reproduce the Problem
1.use same fat image
2.docker-slim build --http-probe=false --include-path-file ./include-paths --include-bin-file ./include-bins fat:latest
3.repeat step 2 sevrail times, watch fat.slim docker size
Specifications
- Version: slim version linux/amd64|Transformer|1.40.7|fc2a26643f26cde441afb267b5a0a17bddc9a897|2023-12-10_07:50:14AM
- Platform: centos7
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by repeatedly running the reported docker-slim build command against the same fat:latest image with --http-probe=false, --include-path-file ./include-paths, and --include-bin-file ./include-bins. Compare the resulting slim image sizes and trace the image-generation path to identify the source of variation; done means repeated runs produce stable output sizes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- build-system, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100