Docker seems to be gaining a lot of momentum and it certainly has a lot of utility for me.

If you want to run Docker on your Linode the first problem to fix is adding AUFS support to the kernel. This can be done using pv-grub and custom kernel (instructions) but as more and more people start using Docker I think it makes sense for Linode to add an AUFS enabled kernel (or at least AUFS as a module).

Unfortunately the second problem to fix is a lot tougher and I don't have any solutions. The tools in aufs-utils need to be installed and, other than Gentoo and Arch, they aren't available in Linode supported distro packages.

Anyway, a certain large competitor to Linode is pushing their support for Docker via OpenStack and it includes a nice repository of docker images.

Is this something we could see from Linode in the future?

Docker works fine in Ubuntu 12.04 I'm using it. As for the kernel it's pretty easy to boot from pv grub. Linode tend to keep the kernel as slim as possible.

_________________
Paid support
How to ask for help
1. Give details of your problem
2. Post any errors
3. Post relevant logs.
4. Don't hide details i.e. your domain, it just makes things harder
5. Be polite or you'll be eaten by a grue

Thanks for this... just looking at AUFS documentation and at the weird aufs-tools source build I didn't even look in the debian/ubuntu repo. Is it in redhat/suse distro's also?



It's easy for you and me, but not everyone which is why I left the "easy" modifier off my statement that we can get AUFS using pv-grub. One could also say it's easy to boot from pv-grub to get XFS support, but thankfully I don't need to because it's in the Linode kernels.



How is this an argument against? My point was that Docker is gaining momentum and thus AUFS will become more useful than many other features that are included in the Linode kernels. On top of that it can be built as a module so it doesn't make the kernel any fatter. It can also be just another selection so if it isn't needed you just pick a kernel that doesn't have AUFS.

From http://www.docker.io/learn_more/

"Please note Docker is currently under heavy developement. It should not be used in production (yet)."

Not a clue I've only tried Ubuntu 12.04 since that's what docker recommend and we're just using it for testing builds (it's really useful being able to spawn up a fresh app server with a clean database in a few seconds)



I didn't say it was, I just said they like to keep things slim, it's rare you'll see a new module added.

_________________
Paid support
How to ask for help
1. Give details of your problem
2. Post any errors
3. Post relevant logs.
4. Don't hide details i.e. your domain, it just makes things harder
5. Be polite or you'll be eaten by a grue

I highly doubt linode would be willing to apply non-mainlined patches to their kernel, since it obviously modifies some fairly core code within the kernel. This completely rules out being able to compile it as a module (as already discussed on the docker page).

The big issue is that this isn't a matter of just enabling some kernel options: AUFS is not part of mainline Linux, and it doesn't appear that it will be included in the future. Debian and Ubuntu distribution kernels are patched to include AUFS, but from what I've seen no other distros do this.

As for the userspace tools, does Ubuntu not include them automatically when you follow Docker's installation steps? ( http://docs.docker.io/en/latest/install ... untulinux/ ) We can't do anything about distributions not offering aufs tools packages.

- Les

The next version of Docker is going to remove the requirement of AUFS, and will depend on device-mapper for snapshots instead.

So wait for 0.7, and hopefully it'll be easier to support on a wider variety of distros.

Docker 0.7 is out, and indeed they did remove the AUFS requirement.

http://blog.docker.io/2013/11/docker-0- ... tribution/

_________________

ヽ༼ຈل͜ຈ༽ﾉ raise your docker ヽ༼ຈل͜ຈ༽ﾉ

_________________
me | voltaireMC

[EDIT]

Looks liek 0.7 Fails too, but for different reasons than the file system:

"lxc-start: failed to create vethSKGOQ0-veth2UJDQE : Operation not supported
2013/11/26 17:39:11 Error: start: Cannot start container 04aa8ba41c1ad6711d0043aeceff6481e5c7dc586c776eb09284cfde3d54f32c: exit status 1"

Anyone else got this to work yet?

This is great news!