Apparently the reason is that it's not compatible with XFS filesystem until 3.12 [6], and even though nobody uses [7] the XFS filesystem, backwards compatibility takes precedence over new features.
This is changed in 3.12, but it looks like the patch just missed the boat for Ubuntu Saucy [8].
[1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/509808
[2] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1085684
[3] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1191600
[4] http://lwn.net/Articles/541787/
[5] http://www.mail-archive.com/[email protected]/msg...
[6] https://news.ycombinator.com/item?id=6761847
[7] By "nobody uses," I mean "I don't use it"
[8] http://lists.debian.org/debian-kernel/2013/09/msg00356.html
I see the convenience argument, which is why people like docker, but basically adding a whole OS overhead to every process you want to run is basically insane in my view.
There is a growing trend of people building micro-containers with just the bare minimum for their application. Docker is facilitating that trend, not preventing it. If only because it explicitly encourages thinking of containers as application-oriented, not machine oriented.
I'm still learning about LXC so my post regarding security may be inaccurate. I'd just thought I'd share it because a lot of people think it's as secure as a virtual machine. I hope soon it is.
"I don't know much about LXC, and I don't know what the defaults are, but I assume that this trivial wrapper around LXC provides more security".
It was just a well intended warning - similiar to the warnings in the Ubuntu docs: https://help.ubuntu.com/12.04/serverguide/lxc.html#lxc-secur... and Gentoo: https://wiki.gentoo.org/wiki/LXC#MAJOR_Temporary_Problems_wi...
Here is the default configuration for Ubuntu 13.10 in comparision: https://gist.github.com/anonymous/7550932
- Without CONFIG_USER_NS and a newer kernel a lot of problematic things can happen. If /proc or /sysfs is mounted on the container DoS or escalation to root is possible: http://blog.bofh.it/debian/id_413 - At the moment no stock distro kernel has CONFIG_USER_NS enabled.
- There are some issues related to remounting filesystems rw and altering files
- Mounting cgroups in the container can also lead to problems - DoS and aquiring more ressources
- Capabilities. You stock Linux distribution won't boot without CAP_SYS_ADMIN (see man 7 capabilities) - there are a lot of other capabilities that could be troublesome.
- Not sure about this one: http://seclists.org/oss-sec/2011/q3/385
So for running services without CAP_SYS_ADMIN and with dropping a lot of other capabilities it can be considered somewhat safe. For everything else it's probably dangerous.
Not sure if all these issues are still a problem today but if you are running lxc on e.g. a current Debian Wheezy you have to know about all of them.