Closed Gowiem closed 3 years ago
@Gowiem I don't know what you are doing to cause this. Our published Alpine image is around 2.25 GB and our Debian image is around 3 GB. Our client images, built on top of Geodesic in a fashion similar to what your Dockerfile looks like, add around 0.5 GB to the image. My guess is that you do not have a proper .dockerignore
file. We recommend this as a start:
@Nuru huh. Let me look into that. I wouldn't think it would be something in the directory that I'm building the image in, but I very well could be wrong. I'll get back with more info.
@Nuru must have been the Dockerignore -- adding that fixed it 👍
Even tho I see the issue was dockerignore here. Just wanted to add that Nuru merger pr #945 which lead to a smaller debian image of geodesic in release 3.0.0!
Additional slim down in:
Also note that the arm64
image is significantly smaller than the amd64
image.
Describe the Feature
When building images on top of debian Geodesic, the resulting image size is ~12gb. This is painful to push a container registry. I'd like to know if there is anything we can do to slim down the size of the Geodesic base image.
Use Case
General use.
Describe Ideal Solution
Cut the image size in half? Provide ways for the consumer to slim down the size?
Alternatives Considered
N/A
Additional Context
Here is my Dockerfile which produces a 11.9gb image: