I'm sorry, I have to be a bit negative on this one.
- No release notes! (as of 1 hour after story posted)
- Network stack re-written. They kinda flubbed network the first time, creating assymetric network and double nat conditions. And within one release, there's a complete re-write with a new networking model? This is going to take a lot of proving to ensure that it's actually going to work for production systems. In the meantime, we at least are going to continue using --net=host for our containers.
- Another storage format. Can we simply get one that's stable, please?
- Volume re-write. Ditto networking.
- [EDIT2] Disregard previous edit entirely - now you're simply disallowed from using devicemapper entirely, if you're using the officially compiled Docker binary for Ubuntu 14.04 and 15.04? [4] What the actual fuck is going on here Docker? AUFS has significant performance issues (not even mentioning the deprecated part), OverlayFS requires a release candidate Linux kernel, ZFS as a storage backend is brand spanking new, and btrfs is as stable as a three legged chair. By the way, this affects CentOS and RHEL.
[EDIT]: 1.7 appears to have fixed the superficial problem - using the wrong devicemapper drivers. Would still prefer to have a proper package.
[ORIGINAL] The whole "devicemapper on Ubuntu 14.4" [1] snafu appears to still in full force [2]. Why can't they offer properly compiled OS packages? They're distributing them as OS/Architecture specific packages...
Note - AUFS is not a real choice for (at least) node applications, we ran into an issue back on 1.6 where there was a low level mutex limiting concurrency on AUFS which did not appear on devicemapper. [3]
Bit new to Docker - so does this mean Docker 1.7 won't work with RHEL? Specifically I'm working on RHEL 6.6 machines, and I'm already stuck with Docker 1.5 so curious to know whether this will affect me
I'm not running RHEL myself, so I can't authoritatively speak about it. The backstory is that Docker, as statically compiled and released, uses the 1.02 release of the devicemapper driver, which has a bug in it. The OS has a 1.02.1 version (and has, for some time, it was patched in Dec 2013), but you have to make your own Docker build which will dynamically link to it.
Take a look at your version of libdevmapper, and you should be able to see if there will be a problem; what I've heard is that CentOS and RHEL also have a fixed version of devicemapper, which causes the mis-match and creates the problem outlined in the #4036 issue.
The ideal fix is to actually compile Docker on an Ubuntu (RHEL) OS when building the Ubuntu (RHEL) packages, but what's actually happening is that it's being built in a minimal Linux container - which gives it a different version.
- No release notes! (as of 1 hour after story posted)
- Network stack re-written. They kinda flubbed network the first time, creating assymetric network and double nat conditions. And within one release, there's a complete re-write with a new networking model? This is going to take a lot of proving to ensure that it's actually going to work for production systems. In the meantime, we at least are going to continue using --net=host for our containers.
- Another storage format. Can we simply get one that's stable, please?
- Volume re-write. Ditto networking.
- [EDIT2] Disregard previous edit entirely - now you're simply disallowed from using devicemapper entirely, if you're using the officially compiled Docker binary for Ubuntu 14.04 and 15.04? [4] What the actual fuck is going on here Docker? AUFS has significant performance issues (not even mentioning the deprecated part), OverlayFS requires a release candidate Linux kernel, ZFS as a storage backend is brand spanking new, and btrfs is as stable as a three legged chair. By the way, this affects CentOS and RHEL.
[EDIT]: 1.7 appears to have fixed the superficial problem - using the wrong devicemapper drivers. Would still prefer to have a proper package.
[ORIGINAL] The whole "devicemapper on Ubuntu 14.4" [1] snafu appears to still in full force [2]. Why can't they offer properly compiled OS packages? They're distributing them as OS/Architecture specific packages...
Note - AUFS is not a real choice for (at least) node applications, we ran into an issue back on 1.6 where there was a low level mutex limiting concurrency on AUFS which did not appear on devicemapper. [3]
-
[1] https://github.com/docker/docker/issues/4036
[2] https://github.com/Capgemini/Apollo/issues/315
[3] https://github.com/docker/docker/issues/13268
[4] https://github.com/docker/docker/issues/14035 (look down for "vbatts" comment with the bolded summary header)