4 ms·

True. However, Linux and Hadoop are very complex beasts that really require and benefit from a lot of expertise when deployed in the enterprise. Perhaps I don't

by weavie 12y ago

True. However, Linux and Hadoop are very complex beasts that really require and benefit from a lot of expertise when deployed in the enterprise. Perhaps I don't fully understand Docker, but really there isn't that much to it. Its a great product and massively useful, but does it really require that extensive knowledge to make the most of it? Docker is really just an extra layer over LXC..

nickstinemates 12y ago
> Docker is really just an extra layer over LXC This is not correct. The Docker engine has an ability to use LXC userland tools as an execution environment, but it is not the primary choice. libcontainer (github.com/docker/libcontainer) is. libcontainer has adoption outside of the Docker world (Parallels, CloudFoundry, as examples) which we find to be a fundamentally good thing. We can also spend time talking about the non-technical values of Docker, if you'd like to jump in to that.
- weavie 12y ago
  Ah, thanks for putting me straight. Yes, please expound. I am largely just a lone developer looking to use docker for my fairly small projects. I currently just use Git for deployment. Is there any value to moving to Docker?
- tinco 12y ago
  Would you say libcontainer is a reimplementation of LXC? Are they related in the sense that they use the same kernel features with the same goal of isolating processes?
  - nickstinemates 12y ago
    I would say that focusing on libcontainer vs. lxc vs. libvirt/libvirt-lxc, lmctfy or any of the container providers is important in how to work with the kernel and expose an API, but in general each have their own relative merits that suit different audiences. We would prefer and encourage for competition to exist at this level, but also to support all of the options with Docker as execution drivers. This is a small example of our approach in general - Instead of locking existing technology out, Docker is designed to integrate seamlessly the choices you're living with today. If we don't do that well, it's a bug. Let's fix it.

by weavie 12y ago

nickstinemates 12y ago

> Docker is really just an extra layer over LXC This is not correct. The Docker engine has an ability to use LXC userland tools as an execution environment, but it is not the primary choice. libcontainer (github.com/docker/libcontainer) is. libcontainer has adoption outside of the Docker world (Parallels, CloudFoundry, as examples) which we find to be a fundamentally good thing. We can also spend time talking about the non-technical values of Docker, if you'd like to jump in to that.

weavie 12y ago
Ah, thanks for putting me straight. Yes, please expound. I am largely just a lone developer looking to use docker for my fairly small projects. I currently just use Git for deployment. Is there any value to moving to Docker?
tinco 12y ago
Would you say libcontainer is a reimplementation of LXC? Are they related in the sense that they use the same kernel features with the same goal of isolating processes?
- nickstinemates 12y ago
  I would say that focusing on libcontainer vs. lxc vs. libvirt/libvirt-lxc, lmctfy or any of the container providers is important in how to work with the kernel and expose an API, but in general each have their own relative merits that suit different audiences. We would prefer and encourage for competition to exist at this level, but also to support all of the options with Docker as execution drivers. This is a small example of our approach in general - Instead of locking existing technology out, Docker is designed to integrate seamlessly the choices you're living with today. If we don't do that well, it's a bug. Let's fix it.