This image uses the CoreOS Alpha channel, which is not supposed to be used for production[1]. It "closely tracks current development work and is released frequ

This image uses the CoreOS Alpha channel, which is not supposed to be used for production[1]. It "closely tracks current development work and is released frequently" so I would be using it with the knowledge that things might break. In other words, CoreOS on DigitalOcean should only be used for trying out CoreOS and not for running production apps (for now). But if I were going to do that, there is already a Vagrant setup[2] that is super easy to use. Hopefully DigitalOcean will provide a CoreOS Stable image soon. On the subject of DigitalOcean images, there was a severe Docker bug[3] the last month or so that made Linux kernel 3.15 unusable. Linode let me easily select a 3.14 kernel to use for my host OS to get around the bug, but DigitalOcean doesn't have that level of granularity. So DigitalOcean either needs to provide more fine-tuned configuration of images or provide a CoreOS Stable image before I would think of using it for production Docker containers. Finally, CoreOS is still an enormous pain[4] to install on Linode, so I hope this gives Linode a strong nudge to make it easier to install there. [1]: https://coreos.com/releases/ https://coreos.com/releases/ [2]: https://coreos.com/docs/running-coreos/platforms/vagrant/ https://coreos.com/docs/running-coreos/platforms/vagrant/ [3]: https://github.com/docker/docker/issues/6345 https://github.com/docker/docker/issues/6345 [4]: http://serverfault.com/a/620513/85897 http://serverfault.com/a/620513/85897