slimtoolkit / slimtoolkit/slim

Unusable resultant CentOS image

Open
#132 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
23.4k
Forks
840
PR merge metrics
No merged PRs in 30d

Description

I using centos image link
next:

docker build -t t2/bo .
docker-slim build t2/bo:centos
docker images
REPOSITORY                                       TAG                 IMAGE ID            CREATED             SIZE
t2/bo.slim                                       latest              37672c536b6e        5 minutes ago       7.04MB
t2/bo                                            centos              df08fdd856fe        57 minutes ago      1.04GB

docker-slim -v
docker-slim version linux|Transformer|1.26.1|2ec04e169b12a87c5286aa09ef44eac1cea2c7a1|2019-11-28_04:37:59PM

With command docker run -it --rm -v /var/run/docker.sock:/var/run/docker.sock dslim/docker-slim build t2/bo:centos I have same issue.

dive show next images:

dive t2/bo:centos

Screenshot_20200219_141543

dive t2/bo.slim

Screenshot_20200219_141412

Result: I have no any system/installed programs like sudo, pm2...

slim report: slim.report.json.gz

dive report: t2-bo.tar.gz

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the report with the CentOS image using the documented docker build and docker-slim build commands, then inspect both results with dive. Compare the slim.report.json.gz and t2-bo.tar.gz attachments to determine why system and installed programs such as sudo and pm2 are absent. Done means the resultant CentOS image retains the required installed programs while still being slimmed.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.