I think the big gap with docker is logging. If you're going down the coreos route you'd probably want your logs centralising somewhere. That means that you need

I think the big gap with docker is logging. If you're going down the coreos route you'd probably want your logs centralising somewhere. That means that you need to configure your containers to run something like supervisord and rsyslog to log to a remote server which is a bit of a hassle, especially if you were making use of public images since you'll need to add all this boilerplate in yourself and rebuild the images. Alternatively I guess you could log to the host if there are config options to log directly to syslog and you could then ship them from there. I spent a couple of weeks writing a python app and the same again trying to sort out a flexible logging system. Ah well, I guess it's still under development, but it'd be great if they prioritised this since it's one of the major things stopping me using docker (and obviously I'm so important they should reprioritise around me!) I really wish coreos was bundled with a package manager though. Not having telnet or the ability to apt-get install things easily makes any sort of debugging and real-world use infeasible for me... :-(