-
Notifications
You must be signed in to change notification settings - Fork 1
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
Work out how to reduce the image size #4
Comments
Here's relevant related issue covering just the |
jsierles
changed the title
Work out how to reduce the final layer size
Work out how to reduce the image size
Feb 17, 2022
This was referenced Feb 18, 2022
Closed
We can open more specific tickets as needed for size optimization. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The image produced by the current setup weighs 340MB. This isn't terrible for a typical Rails image, but could be a lot smaller based on what's visible in the image.
Using dive we see a large 245MB layer at the bottom. This layer contains the source code, rubygems, and the rubygems dependencies. This means that every code change will require pushing a 245MB layer. Let's see how we can improve this.
Here are tickets describing specific options to explore:
pg
gem in Nixpkgs to depend onpostgresql.lib
to reduce the closure size #6The text was updated successfully, but these errors were encountered: