I don't use phusion/baseimage, but I'm not against it existing. I would, however, like to clarify a couple of things in your two blog posts today: 1. "we are

I don't use phusion/baseimage, but I'm not against it existing. I would, however, like to clarify a couple of things in your two blog posts today: 1. "we are the most popular third party image on the Docker Registry". This is true based on the # of stars, but that can be misleading when you look at the actual number of pulls. Don't get me wrong, phusion/baseimage is popular with about 230k pulls, but if you look around there are dozens of images with millions of downloads, so your claims are a bit misleading. 2. phusion/baseimage inherits from the official ubuntu:14.04 image. It adds a lot of things, and starts a number of services by default, so it is absolutely a "fat" VM-like container. I'm not against this at all, but I will point out that the Dockerfile Best Practices article (http://docs.docker.com/articles/dockerfile_best-practices/ http://docs.docker.com/articles/dockerfile_best-practices/) is explicit that a container should kick off one process. If you look at how the highly curated official repositories function, none of them run more than one process or utilize a supervisor. Docker gives you the freedom to do whatever you want, but calling phusion/baseimage a "correct" way to do Docker conflicts with the official documentation. I totally get that phusion/baseimage has been around for a long time, and provides solutions to some common problems which may make adoption easier for some with legacy apps, but I would refrain from claiming that your solutions "gets everything right". By all means, use whatever works, just be aware that the best practices are clearly outlined on docs.docker.com, not the Phusion blog.