Extend and improve dynohost with tools such as http://docker.io

[Filirom1]

Docker and CloudFoundry Warden add abstraction on LXC and cgroups/namespace.

It's interesting to check if it's better to use those projects or to stay on LXC.

LXC is moving too. Version 0.9 will be released soon and version 1.0 (Feb 2014) will allow us to create new containers without being root : http://sourceforge.net/mailarchive/forum.php?thread_name=5122B0A9.4020508%40ubuntu.com&forum_name=lxc-devel

About docker.io there are some features that do not fit well with Heroku philosophy :

• Filesystem isolation : in Heroku root filesystem is mount in read only , and /app and /tmp are the only two directories with write access
• Network isolation : also provided with LXC with this PR Openruko - Using a full ubuntu OS #8. This feature is currently in labs at Heroku : https://devcenter.heroku.com/articles/containerized-network
• Copy-on-write : not needed because /app and /tmp are by default empty or filed with the slug. Other directories are ready only
• Logging : docker bufferize logs but Heroku stream logs : https://blog.heroku.com/archives/2010/12/13/logging. Philosophy are different : http://adam.heroku.com/past/2011/4/1/logs_are_streams_not_files/

Docker depends on AUFS, it's only available by default on Ubuntu's kernel.

[progrium]

Docker was designed to be a Heroku dyno manager primitive. It's just slightly lower level. So, for each point:

• filesystem isolation: you can make this happen within a container.
• network isolation: dockers net isolation is also designed to be like heroku's, but inter-container networking is not done yet
• copy-on-write: this is actually how heroku dyno's actually work. /app and /tmp are writable in a copy on write fashion. if you were allowed to write in any other directory, it would also be copy on write.
• logging: docker lets you inspect logs buffered as a convenience, but you can attach to a process to stream stdout/stderr (or stdin). this is similar to heroku's architecture in that you can attach to a dyno via rendezvous url

[Filirom1]

Thanks for the clarification

It looks really great :)