Slashdot Mirror
Docker Turns 1: What's the Future For Open Source Container Tech?
darthcamaro (735685) writes "Docker has become one of the most hyped open-source projects in recent years, making it hard to believe the project only started one year ago. In that one year, Docker has now gained the support of Red Hat and other major Linux vendors. What does the future hold for Docker? Will it overtake other forms of virtualization or will it just be a curiosity?"
Isn't docker just a wrapper around real container techs? (union filesystems, cgroups/namespaces/containers (lxc basically), etc) with a cloud-init style deployment script?
Docker has become one of the most hyped open-source projects in recent years
The pants? Yeah, those are OK. They don't last that well.
If I've heard of Docker once before, I don't remember it.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
slashvertisment
The idea of docker is cool but the implementation needs works. It's pretty complicated to understand compared to say VMware or VirtualBox. Especially the versioning stuff, it's really annoying. It's like combining git or svn and virtual machines. You get the obscure weird architecture of a version control system combined with the configuration complexity of a VM. It's pretty confusing even for seasoned professionals.
My wife says my ass looks good in Dockers.
Since nobody else is commenting, I guess that I'm not the only one that had never heard of Docker.
The story doesn't bother to summarize what Docker is. Or even give a link to an explanation. That may not be completely unreasonable, because it's hard to find any understandable information on the main website either. Apparently a "container" is a method of delivering an application that is geared towards VMs and cloud computing, but that's about all I got out of it.
How can we continue to believe in a just universe and freedom to eat crackers if we have no ale?
She's probably just comparing it to what it looks like out of Dockers.
... but rationalizing it. Sometimes you just need to run more or less isolated single apps, not for a full blown OS. In a lot of usage scenarios is far more efficient, (both in disk/memory/cpu usage and app density) and probably more flexible. In others full OS virtualization or running on dedicated hardware may be the best option.
It also brings a virtualization-like approach for apps in the cloud. You can have cointainerized apps in aws, google apps and many others, something like having a vm inside a vm.
Is not the only solution of its kind. Google is heavily using containers in Omega (you can try their container stack with lmctfy), you can use openvz, lxc, or solaris zones or bsd jails. But the way that docker mixes containers (not just lxc by 0.9) with union fs, making them portable and to have inheritance, is a touch of genius.
The missing pieces are being added by different projects. CoreOS as a dedicated OS for containers (that coupled with etcd and fleet could become a big player in a near future), OpenStack/OpenShift bringing manageability, and maybe someone could bring to the table what Omega does with google containers.
But.. but.. aren't you amazed?!? It's only been a year since that thing you never heard of did something you aren't being told?!?!! Who says journalism is dead?
Link 1: Wow, look how much uses Docker!
Link 2: Okay, docker works as some sort of VMy thing, oh and hype hype hype in case you missed link #1.
I rarely complain about FPs, even blatant Slashvertisements... But seriously? Yay, something wildly successful (that I've never heard of) has lasted a year. Woo-hoo! Pass me a beer.
Is this some kind of user-space open-mosix?
Advertising a program as "one of the most hyped" seems contradictory to me (in addition to factually incorrect, as most people have never heard of it). If something is hyped, doesn't that mean it's not worth its publicuty?
Docker is being hyped by developers because they think it will let them route around system administators.
Go ahead, deploy cloned images of your junk code, with its hotch-potch mix of ruby gems and java libraries, all dragged down from pre-alpha github repositories and deploy it straight to production from Jenkins.
Let's see how far you get recompiling your code when the only security fixes available for that obscure library you decided to use against the advice of your sysadmins, are from HEAD and introduce several backwards incompatible changes to the API.
It's time to collectively make developers pull their heads in. Develop only using libraries packaged for your OS (be it debs, rpms, whatever) with good security support. If they need libraries outside those, they need to justify it, and produce good OS packages and have the ability to backport security fixes to them, to prevent breaking APIs.
Sun, when it still shone, used containers heavily, because they made "dedicate a machine" trivial.
You could give a product or product suite a dedicated machine, and have netstat or vnstat report on just the behavior of the one program. You could clone a copy of production for the developers to base their next release on, you could hand a release to QA to test hand have them hand it back, and finally you could hand a tested machine to production to start exposure testing.
This allowed a much more agile cycle than having to re-install a product for development, install it again for test, then fail to reproduce a problem and have tor reinstall both, and finally reinstall the "fixed" config on prod and have the bug come back! Far better quality, and far less work.
I'm a capacity planner, so I liked it because I could give a "machine" a minimum guarantee of 20% of a 64-cpu machine, and know that it it would give back the capacity it didn't use, something that "hard" LPARS can't do.
davecb@spamcop.net
I had never heard of "Docker" before today, nor heard any hype about it.
Get free satoshi (Bitcoin) and Dogecoins
You say that like its a bad thing.
Having to work for a living is the root of all evil.
Run a minimalistic Linux box? Check.
Put software on a virtual disk so I can chroot with a restriction to the device? Check.
Build software statically linked to the libraries in the build directory so they don't need access to the rest of the system? Check.
Know that it would be popular and might make monies? Doh!
Having to work for a living is the root of all evil.
I just read this past week that Docker is moving away from LXC to implement its own driver (libcontainer).
Not sure whether or not this is a good thing or whether it will distract from the great work being done in LXC.
LXC 1.0 was "just" released and implements a multitude of great new features including "unprivileged" containers.