4 ms·
> automates the deployment of any application as a lightweight, portable, self-sufficient container that will run virtually anywhere. Bullshit. How do I run i
by rdtsc 13y ago
> automates the deployment of any application as a lightweight, portable, self-sufficient container that will run virtually anywhere.
Bullshit. How do I run it on RHEL 5, because DoD systems are chock full of those? What about Windows? I have to install Virtualbox, and Vagrant and then run Docker inside the virtualized linux environment and then run docker containers in that.
So "virtually anywhere" means on a handful of systems.
Sometimes technology's biggest "fans" are its biggest enemies without even realizing.
- Aqueous 13y agoI really wish Apple, for instance, would enable the same process/network namespacing that enables LXC to work. I'm not sure what the state of Windows is with respect to virtual network namespaces and process namespaces and control groups, but if the two other major OSes enable these basic features, it is easy to imagine universal containers that run everywhere.
- rdtsc 13y agoApple could choose to support LXC. FreeBSD systems have jails, so another way forward was if Apple support that, Docker could wrap a generic API on top of that. Much like libvirt is doing with various VM hosting solutions.
- nickstinemates 13y agoOr Docker could gracefully degrade to using chroot on OS X (providing a different type of isolation.) This is a plan. One of the things Docker needs to get better at expressing is that A Docker container != Linux Containers. It may currently Build/Provision/Execute inside of a Linux Container (provided by LXC) but that is an (albeit important) implementation detail.
- kulkarnic 13y agoThat is unnecessarily harsh. Docker legitimately represents a new idea, and some claim, a better idea. Yes, it won't run on RHEL5; but Java probably did not run on DEC mainframes either (back when its selling point was Write once run anywhere). The question seems to be this: does this container model represent a step forward? I think it does. (And is it hyped a bit too much? Probably :-)
- rdtsc 13y ago> That is unnecessarily harsh. So do you agree that it runs "virtually anywhere" is bullshit or not. I say it is. Is Windows antiquated too? What about Mac OS X? It is harsh vis-a-vis the claim it makes. If it makes revolutionary claims, it better hold up to harsh criticism. > Docker legitimately represents a new idea, and some claim, I agree with that. So "Investigating container models for application deployment" title?
- jpetazzo 13y agoI don't know yet what will happen for Windows, but an upcoming version of Docker will run on OS X. (I say "upcoming" because I know some core maintainers have OS X support in their local branches, so it's just a matter of time before it hits master.) It doesn't has the same isolation guarantees (yet) but it lets you use the same workflow. Windows is different, but I can't imagine a scenario where you have to run your app on Windows. I.e. if it's your local machine, you can spin up a VM; if it's in your datacenter, you can use Linux. If your local policies are "we only run Windows on our servers, screw Linux!" chances are that you wouldn't run Docker anyway, even if it ran natively on Windows :-)
- wmf 13y agoLinux/x86-64 Docker images (which is all of them) aren't going to run on OS X unless inside a VM.
- luuse 13y agoI'd say RHEL 5 is fairly outdated and that Windows is irrelevant for a non negligible portion of development shops as a development platform and as a deployment platform. I don't agree with that it would run "virtually anywhere" but it should at least run on every platform that has binary compatibility with the platform that a container was built for? Getting docker to work on Windows might take a while but Mac could work. I actually do think Docker or at least the container model will change a lot, i'm considering staying with Linux as my development platform instead of Mac and that's a thought i'd have laughed at two years ago and the sole reason is Docker.
- jfoutz 13y agoGiven the rest of the article, I think anywhere means any cloud host other than joynet.
- 3am 13y agoAnd they're not portable, either! What kernel is Ruby 2.0.0 build against on in his example? Maybe Docker itself may be everywhere, but you still have have to be aware of any OS dependencies that apps in your Docker container might have... I think lxc+cgroups and Docker are a much less wasteful way to provision lots of similar systems with particular types of workloads, but this article did seem a little hyperbolic.
- shykes 13y agoIn practice though a very large majority of applications are already expected to support a wide range of kernel versions and flavors, and require zero modifications to do so because of Linux's outstanding track record of preserving reverse compatibility. So deploying an application as a container is a big improvement over shipping it as source or package, because instead of having to support any combination of library versions, distros and kernels, it only needs to worry about the kernel which is the easiest part.
- danudey 13y agoSure, but if you're looking at systems running the latest RHEL, there's a lot of stuff you don't get. RHEL5, when it shipped at least, didn't have memcached. RHEL has always appealed to IT departments and server staff who value stability over functionality, much like corporate IT at the hospital where I worked finally approved Windows XP SP1 for test deploys, well after SP3 had been released. They don't want to risk the headache, so they stick with what works rather than providing functionality (or compatibility) that others could need. There's definitely value in that, don't get me wrong, but my point is that the types of environments where RHEL5 are the norm wouldn't be rolling out Docker instances even if they could, and I don't feel as if they should be counted against the impact of progress.
- rdtsc 13y agoBut a lot of servers and platforms out there don't run on this years' Linux kernel. That is a far cry from "virtually anywhere" which was my original issue with this blogpost. I am not arguing that I need Docker to run on RHEL personally or I need it to run in Windows. The point was about making unsubstantiated claims about a product and in the meantime while seemingly trying to help "market" the product now putting the creators on the defense having to backpedal. "Well no, contrary to what some of your may have read from our zealous followers, we don't don't run virtually anywhere. Here is a list of Linux distros we run out of the box on. Here is a list where you'll need to installed a custom kernel."
- zenocon 13y agoVMWare has had a similar concept called ThinApp for Windows http://www.vmware.com/products/thinapp/ http://www.vmware.com/products/thinapp/ -- albeit it is more geared towards desktop apps as opposed to server apps, but similar concept. If I recall it was an acquisition for them 4-5 years ago.
- pan69 13y ago>> Bullshit. It's actually promoted like that on their website: http://www.docker.io/learn_more/ http://www.docker.io/learn_more/
- rdtsc 13y agoWell, so it is. It doesn't make it less bullshitty. It changes that fact that it wasn't only a zealous fan driving up some excitement, they are doing it themselves. Well,I don't like it. I don't like when tech companies selling to developers mislead them or make over-inflated statements. Let 2am infomercials do that. MongoDB was (is?) in the same category, and I don't trust them and don't like their product. Can you imagine Linus writing the new kernel version announcement like that -- "This kernel release will run anywhere. It will radically change how you look at the world. It might bring about peace too". What over-inflated claims do is break trust. If they are marketing for non-technical people, yes general statements work. Marketing to other technical people using claims like that is patronizing and disappointing.
- shykes 13y agoYou're right, today there are many systems which cannot run docker. There are several things we are doing to remediate that. Obviously there are no miracles, if you run a kernel which doesn't support namespacing, you won't get namespacing :) However: * We can make the "docker in a vm" option much better. In another thread I mentioned boot2docker (http://github.com/steeve/boot2docker http://github.com/steeve/boot2docker) which is the smallest possible VM to run docker - currently 25MB. Of course there is a performance tradeoff but for, say, a developer's mac or a server which is underutilized anyway, it may be exactly what you need. * We are adding swappable execution drivers to docker, so that you can replace lxc (the current default) with openvz, or gracefully degrade to a simple chroot. Also a tradeoff - obviously you get very little guarantees of isolation, but for production servers which only run trusted payloads and don't need to extra resource isolation within each server, it is a great option. In both cases, you still get the benefit of a unique (as in byte-for-byte unique) payload which can be transferred across machines and executed with strong guarantees of repeatability and consistency. That is often a big improvement from shipping provisioning scripts which will dynamically pull dependencies each time, giving you "good enough" repeatability at best. Maybe you forgot to pin a dependency and the mirror was updated between 2 deploys? Maybe the python build on Fedora (staging machine) is not the same as on RHEL (production). Docker solves that. Yes, there are caveats and it's not a silver bullet. And yes, god knows it is over-hyped. But the claims are not bullshit :)
- rdtsc 13y ago> You're right, today there are many systems which cannot run docker. It would be better if you put a footer or a developer's view of the technology, otherwise overarching claims about its features could back-fire. MongoDB over-marketed themselves vis-a-vis the features it actually provided. I think there is no shame in saying we use LXC container technology. We can run on these systems patched, on these with a custom kernel, on these inside a VM. "Virtually anywhere is a bit of a stretch" I think. * We are adding swappable execution drivers to docker, so that you can replace lxc (the current default) with openvz, or gracefully degrade to a simple chroot. That is a cool feature, I like it. Libvirt does this for regular VMs. > In both cases, you still get the benefit of a unique (as in byte-for-byte unique) payload which can be transferred across machines and executed with strong guarantees of repeatability and consistency. Good stuff. That sounds like a good plan. What about a Docker cluster (or maybe you already have that and I am showing my ignorance here). Run docker on a variant of host platforms and docker containers could contain tags that identify what kernel/distro/arch is needed and it would be automatically started/migrated to that host. But it would done rather transparently. Low resource VMs will be something hosting providers will jump on as that is direct money in the pocket (can put more lightweight VMs on a physical host). But instead of having a generic set of uniform host, they'd just provide the right mix of dist/kernel/arch flavors, underneath. "Oh look people love their Ubuntu 13.10 servers, quickly add more Ubuntu hosts" stuff like that. > Docker solves that. Docker is good stuff. I like. My criticism was not of Docker's product but its marketing.