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

Open
Filirom1 opened this Issue Mar 29, 2013 · 2 comments

Comments

Projects
None yet
2 participants
@Filirom1
Owner

Filirom1 commented Mar 29, 2013

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 :

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

@progrium

This comment has been minimized.

Show comment Hide comment
@progrium

progrium Mar 29, 2013

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

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

This comment has been minimized.

Show comment Hide comment
@Filirom1

Filirom1 Mar 29, 2013

Owner

Thanks for the clarification

It looks really great :)

Owner

Filirom1 commented Mar 29, 2013

Thanks for the clarification

It looks really great :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment