Re: [Users] Users Digest, Vol 25, Issue 120
This is a multi-part message in MIME format. --------------090008020700000302020801 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 10/25/2013 04:41 AM, users-request@ovirt.org wrote: I haven't looked into this very much, but it sounds promising. Anyone on list familiar with it? It is, in essence, LXC containers combined with an overlay filesystem. It's basic PaaS with a Go binary ("docker") wrapped around LXC. It's neat in the same sense as Vagrant -- you can ship a Dockerfile which can reproduce your environment very easily, and the Docker team itself has wrapped all the images in a git repository you can easily branch from/etc. That said, Docker support won't land in Fedora until F20, and CentOS around the same time (officially). I'll admit that I don't get the hype around Docker, since it doesn't do anything that LXC doesn't already do, but the templating and a user-friendly binary is nice. I wonder if there's interest in shipping oVirt docker containers. I'm interested in Docker to ease the process of building Node images, at least. oVirt Docker containers would be interesting, assuming LXC support isn't painful, since the CoreOS (where Docker originated) also relies on an image with readonly root and overlays on top, so there's some overlap. --------------090008020700000302020801 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body text="#000000" bgcolor="#FFFFFF"> <br> <div class="moz-cite-prefix">On 10/25/2013 04:41 AM, <a class="moz-txt-link-abbreviated" href="mailto:users-request@ovirt.org">users-request@ovirt.org</a> wrote:<br> <blockquote> I haven't looked into this very much, but it sounds promising. Anyone on list familiar with it?</blockquote> </div> It is, in essence, LXC containers combined with an overlay filesystem. It's basic PaaS with a Go binary ("docker") wrapped around LXC. It's neat in the same sense as Vagrant -- you can ship a Dockerfile which can reproduce your environment very easily, and the Docker team itself has wrapped all the images in a git repository you can easily branch from/etc. That said, Docker support won't land in Fedora until F20, and CentOS around the same time (officially). <br> <br> I'll admit that I don't get the hype around Docker, since it doesn't do anything that LXC doesn't already do, but the templating and a user-friendly binary is nice. <blockquote> <pre wrap="">I wonder if there's interest in shipping oVirt docker containers.</pre> </blockquote> I'm interested in Docker to ease the process of building Node images, at least. oVirt Docker containers would be interesting, assuming LXC support isn't painful, since the CoreOS (where Docker originated) also relies on an image with readonly root and overlays on top, so there's some overlap.<br> </body> </html> --------------090008020700000302020801--
Am Freitag, den 25.10.2013, 07:31 -0700 schrieb Ryan Barry:
On 10/25/2013 04:41 AM, users-request@ovirt.org wrote: I haven't looked into this very much, but it sounds promising. Anyone on list familiar with it? It is, in essence, LXC containers combined with an overlay filesystem. It's basic PaaS with a Go binary ("docker") wrapped around LXC. It's neat in the same sense as Vagrant -- you can ship a Dockerfile which can reproduce your environment very easily, and the Docker team itself has wrapped all the images in a git repository you can easily branch from/etc. That said, Docker support won't land in Fedora until F20, and CentOS around the same time (officially).
I'll admit that I don't get the hype around Docker, since it doesn't do anything that LXC doesn't already do, but the templating and a user-friendly binary is nice. I wonder if there's interest in shipping oVirt docker containers. I'm interested in Docker to ease the process of building Node images, at least. oVirt Docker containers would be interesting, assuming LXC support isn't painful, since the CoreOS (where Docker originated) also relies on an image with readonly root and overlays on top, so there's some overlap.
One "nasty" secret of CoreOS is that they are using aufs - a fuse overlay fs - and that's just not nice. All this stuff requires a decent union-mount support. Just my 2ct. Otherwise it's also totally interesting! - fabian
participants (2)
-
Fabian Deutsch -
Ryan Barry