Skip to content
This repository has been archived by the owner. It is now read-only.

Look into reducing base image size #62

Closed
fgrehm opened this issue Aug 5, 2014 · 2 comments
Closed

Look into reducing base image size #62

fgrehm opened this issue Aug 5, 2014 · 2 comments

Comments

@fgrehm
Copy link
Owner

@fgrehm fgrehm commented Aug 5, 2014

@fgrehm fgrehm added this to the v0.2.0 milestone Aug 5, 2014
@fgrehm fgrehm added enhancement and removed enhancement labels Aug 22, 2014
@fgrehm fgrehm modified the milestones: v0.2.0, v0.3.0 Sep 8, 2014
@fgrehm
Copy link
Owner Author

@fgrehm fgrehm commented Sep 8, 2014

Switching to progrium/cedarish:cedar14 lowered the base image from 1.168GB to 867.7MB for v0.2.0, we can lower it even more by removing nodejs, bazaar, mercurial and possibly other stuff from the base and I'll look into it on 0.3.0

@fgrehm fgrehm added the 2 - Working label Sep 8, 2014
@fgrehm fgrehm modified the milestones: v0.3.0, v0.2.0 Sep 9, 2014
@fgrehm fgrehm added 0 - Backlog and removed 2 - Working labels Sep 9, 2014
@fgrehm fgrehm added 2 - Working and removed 0 - Backlog labels Oct 23, 2014
@fgrehm fgrehm modified the milestone: v0.3.0 Jan 15, 2015
@fgrehm
Copy link
Owner Author

@fgrehm fgrehm commented Jul 7, 2015

Heroku's cedar image is around 1.2GB and 0.4.0 is at 1.4GB, can't do much here besides moving on to another base which I don't see happening anytime soon =/

Ideas on how to handle this are welcomed!

@fgrehm fgrehm closed this Jul 7, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.