Comments on: Favorites from GitHub Universe

By: rudijs

rudijs — Fri, 12 Feb 2016 06:54:00 +0000

For Node.js web apps, shouldn’t there’s be a process manager to restart the server if it crashes? A process manger like PM2, forever or strongloop’s Arc.

By: Michał Gryko

Michał Gryko — Tue, 09 Feb 2016 07:34:00 +0000

Nice idea in overall, great that people finally see that containers should contain only app + its dependency. I’ve created very basic version of such build tool for my previous company: https://github.com/Playsoft/container_builder It saved us lot of disk space and time on container pull. I didn’t understood this “FROM ubuntu” Dockerfiles from very beginning. It feels so heavy.

By: zoobab

zoobab — Thu, 04 Feb 2016 10:05:00 +0000

I made even smaller images with openwrt (basically the rootfs is mostly just busybox). 5MB.

By: James Mills

James Mills — Thu, 04 Feb 2016 07:29:00 +0000

I don’t mean to be a cynic; but this is all based around Alpine. Several or more of us in the community have already done all this (including myself for Python). What is so special about what iron.io have done or provide really?

By: Ralph Tice

Ralph Tice — Wed, 03 Feb 2016 23:58:00 +0000

Have fun troubleshooting really insane seg faults because of musl instead of glibc. I’ve had some fun ones with both python and Oracle JDK. Just getting the Oracle JDK running at all involves wget’ing some random glibc bits from circleci.

By: treeder

treeder — Wed, 27 Jan 2016 18:31:00 +0000

In reply to Harlow Ward. I don't think there's an advantage to build it either way, you should end up with the same bin eight way. I just like building inside containers regardless so I don't have to setup anything on my machine to do it (GOPATH, etc) and if it's not static, you can build/test on whatever system you are going to be running on. For instance, a Go binary built on Ubuntu will not run on Alpine, so just build it inside an Alpine container and you're good to go. And you can test it on the destination operating system too.

By: Dave Newton

Dave Newton — Wed, 27 Jan 2016 17:45:00 +0000

In reply to Rémi Alvergnat. But the generalized base container would still be the same, and the specialized images would still have the same stuff. I think you'd need a pretty wide swath of micro images to add up to even a few macro images.

By: Rémi Alvergnat

Rémi Alvergnat — Wed, 27 Jan 2016 09:09:00 +0000

Great post, thanks ! Micro containers are often better, people should keep in mind that if you have 10 container sharing the same big 650Mb image, it won’t eat 10x650Mb, but 1x650Mb.

So if size matters for ease of distribution and public images, I’m not sure it’s that critical and it can even be counter-productive in some case.

If host runs 10 containers based on 10 distinct micro image, it might eat up more space that it would by using a single bigger and more generalist base image …

By: Harlow Ward

Harlow Ward — Tue, 26 Jan 2016 21:37:00 +0000

Great post @treeder:disqus . Can you expand on the advantage of building the Golang static binary inside the Docker container as opposed to building with `GOOS` and `GOARCH` ENV vars on command line?

By: treeder

treeder — Tue, 26 Jan 2016 17:40:00 +0000

In reply to naxhh. Ya, the layers don't show the size decrease for some reason, but the total image size is much smaller. In iron/node, we uninstall npm and it cuts the image size down by something like 20MB. Even though the layer for npm uninstall shows 0.