Docker image size is blowing up
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- docker, python
- Domain
- build-system, infrastructure
Research direction
Start by comparing the Docker image layers and build history for v125 and v129 using the linked Google Container Registry image. Identify which release changes account for the growth, then verify that a subsequent image no longer increases at the reported rate while preserving the image's existing contents.
Written by the indexing model from the issue text.
Description
When comparing the last few releases in
https://console.cloud.google.com/gcr/images/kaggle-images/GLOBAL/python
it is quite noticeable that recently there has been a sudden increase in the docker image size, e.g. from virtual size 6.2 GB of v125 to virtual size of 8.3 GB of v129, i.e. a 34% increase.
When uncompressed, docker reports that v125 results in a 19 GB container, while v129 results in a 23 GB container, i.e. a 21% increase.
I noticed this while running (the heaviest of) my workflows on GitHub Actions, randomly getting errors like
System.IO.IOException: No space left on device : '/home/runner/runners/2.302.1/_diag/Worker_20230304-204952-utc.log'
While surely the amount of disk space that GitHub offers is not your responsibility, you may still want to check if there is any way to keep the size of the docker image under control, and if possible keep it from growing at this rate any further.
- Dominant language
- Python
- Stars
- 2.7k
- Forks
- 1k
- Avg merge
- 5h 55m
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
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.
More from Kaggle/docker-python
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Kaggle/docker-python#1482 · 2 reactions ·
-
ذ Open
Difficulty 5/5 Over a week Newbie friendliness 1/100
Kaggle/docker-python#1555 ·
-
bug help wanted
Difficulty 4/5 3-5 days Newbie friendliness 42/100
Kaggle/docker-python#1546 · 4 comments · 2 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Kaggle/docker-python#1515 ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
Kaggle/docker-python#1506 · 1 reaction ·
All issues in Kaggle/docker-python
Similar issues
-
bug confirmed issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
open-webui/open-webui#30750 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
OpenwaterHealth/openmotion-bloodflow-app#604 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
good first issue
Difficulty 1/5 Under an hour Newbie friendliness 90/100