utilities/auto-blog-link-preserver#18: Docker image contains a 600MB layer



Issue Information

Issue Type: issue
Status: closed
Reported By: btasker
Assigned To: btasker

Milestone: v0.1
Created: 11-Aug-24 14:21



Description

When pushing the image, there's a 587MB layer.

bb45ff6c69ae: Pushed 
67ad16dc1c08: Pushed 
ffe60aac26fc: Pushing [===================================>               ]  416.9MB/587.4MB
0905150af928: Pushed 
7cfafa82cfd2: Pushed 


Toggle State Changes

Activity


assigned to @btasker

It looks like it might be part of the image we're based on, but either way we should really see if we can squash that away.

Looks like it just is that big :(

docker history ghcr.io/bentasker/auto-blog-link-preserver:0.1
IMAGE          CREATED          CREATED BY                            SIZE      COMMENT
9ba3dabf538b   36 seconds ago   CMD ["/bin/sh" "-c" "/app/main.py"]   0B        buildkit.dockerfile.v0
<missing>      36 seconds ago   USER rssfeed                          0B        buildkit.dockerfile.v0
<missing>      36 seconds ago   ENV FEEDS_FILE=/app/feeds.json        0B        buildkit.dockerfile.v0
<missing>      36 seconds ago   ENV HASH_DIR=/hashdir/                0B        buildkit.dockerfile.v0
<missing>      36 seconds ago   ENV PYTHONUNBUFFERED=1                0B        buildkit.dockerfile.v0
<missing>      36 seconds ago   COPY / / # buildkit                   1.04GB    buildkit.dockerfile.v0

Lets move to the alpine base image then - bit hard to justify a 1GB image for a small cronjob.

verified

mentioned in commit 392144e86c1827716217310d5dd56dcaa49031fd

Commit: 392144e86c1827716217310d5dd56dcaa49031fd 
Author: B Tasker                            
                            
Date: 2024-08-11T15:32:03.000+01:00 

Message

fix: move to using alpine base image (utilities/auto-blog-link-preserver#18)

+2 -2 (4 lines changed)