Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reduce size of v4 minimal image #197

Closed
git-developer opened this issue Apr 14, 2024 · 2 comments · Fixed by #228
Closed

Reduce size of v4 minimal image #197

git-developer opened this issue Apr 14, 2024 · 2 comments · Fixed by #228

Comments

@git-developer
Copy link
Contributor

(Migrated from #115)

This is a request to reduce the size of the v4 minimal image.

The minimal image has grown significantly between v3 and v4:

$ docker images | grep fhem
ghcr.io/fhem/fhem-minimal-docker   3.3.1-bullseye                       c9b1f0c873e7   4 months ago    635MB
ghcr.io/fhem/fhem-minimal-docker   dev-bullseye                         cf28244b08a3   12 hours ago    905MB

Maybe a switch to the slim base image helps (not verified).

$ docker image ls | grep perl
perl                 5.36.3-slim-bullseye   52a305760451   3 weeks ago     132MB
perl                 5.36.3-bullseye        61325f916a7e   3 weeks ago     692MB
@sidey79
Copy link
Contributor

sidey79 commented Apr 14, 2024

Maybe this ist possible, during Installation of CPAN modules they need some build tools.

We can try to copy all cpan modules later to a slim based image layer. But first goal ist to get rid of some build bugs.

@sidey79 sidey79 linked a pull request May 5, 2024 that will close this issue
@git-developer
Copy link
Contributor Author

$ docker image ls | grep fhem
ghcr.io/fhem/fhem-minimal-docker   dev-bullseye                         e9e2497c9e17   7 hours ago      531MB
ghcr.io/fhem/fhem-minimal-docker   3.3.1-bullseye                       c9b1f0c873e7   5 months ago     635MB

Thanks a lot!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

2 participants