HNHacker News
TopNewBestAskShowJobs

jbergknoff

507 karma · joined October 20, 2014

submissionscomments
jbergknoff··on Toolkit
If you have docker installed, you can use this 9 MB sass image instead of installing ruby or compiling node-sass: https://registry.hub.docker.com/u/jbergknoff/sass/
jbergknoff··on Rewriting RubyGems.org Git History
It would be really helpful to go into some detail on the steps taken to clean up the git history.
jbergknoff··on Coming Soon – AWS SDK for Go
The node.js library [1] is incredibly well done. It's easily the best-documented node.js library I've ever seen.

[1] https://github.com/aws/aws-sdk-js

jbergknoff··on Building Good Docker Images
You're right that a published Dockerfile isn't enough to really know what went into the image, but I think it's the closest thing we have at the moment. I would love to see some tools for building truly minimal docker images from scratch.
jbergknoff··on Building Good Docker Images
Thanks for pointing this out. In the "debian:wheezy" docker image, "apt-get clean" didn't seem to have an effect. I dug around a bit and found that, in this image, aptitude is configured to not cache the downloaded packages (via /etc/apt/apt.conf.d/docker-clean).

On one hand, I consider this a good default behavior for building docker containers, so I'm glad it's there. On the other hand, I didn't know about it until I investigated. It's strong evidence for the great point @amouat made regarding base images being blackboxes in most (all?) cases.

← PreviousPage 3 of 3