Docker in Docker
Docker restricts (a lot!) the capabilities of the containers it runs.
Some of those capabilities are needed in order to run "sub-containers".
Using the --privileged flag (introduced in 0.6), it is now possible
(and relatively easy) to run Docker within Docker. It is even possible
to run Docker within Docker within Docker.
Here is a list of the things that have to be done in order to run Docker (and containers) within a Docker container.
You need net_raw (for iptables), and sys_admin (for namespaces,
and possibly many other things).
--privileged addresses this.
I ended up disabling AppArmor altogether, because finding the exact permissions was cumbersome, and it looks like some permissions could not be expressed exactly.
To disable AppArmor, but still get information about which AppArmor
mechanisms were involved, I edited /etc/apparmor.d/lxc/lxc-default,
and changed the flags to add complain. In my case, the flags became
flags=(attach_disconnected,mediate_deleted,complain).
If you want, you can also try to be fine-grained; you will at least need
to enable AUFS mounts (mount fstype=aufs) but there will be other things
to do.
Note: on my Ubuntu LTS 12.04 test machine, Docker-in-Docker worked out of the box. However, I got reports that it didn't work on 13.04 because of some AppArmor issues. This is very curious, since newer versions were supposed to improve the situation for nested LXC containers.
Since AUFS branches cannot sit on an AUFS filesystem, make sure that
/var/lib/docker is a volume, or a bind-mount, or a local tmpfs mount.
Otherwise, the nested Docker won't be able to create AUFS mounts on it.
Make sure that cgroups are mounted within the container. You can do
this manually. You can also use the cgroups-mount helper, for convenience.
However, I don't remember where this helper comes from :-)
Sometimes, if cgroups-mount doesn't work, you can try:
umount /sys/fs/cgroup ; cgroups-mount
It worked all the time for me.
In my dind implementation, I wrote a small wrapper script to manually mount cgroups before starting the Docker daemon.
Of course, this requires the --privileged flag.
When I tried to run Docker in Docker, the LXC userland tools were not
very cooperative. Namely, lxc-start tries to remove CAP_SYS_BOOT,
and bombs out it the capability was already removed (!). Since this
capability is unconditionally removed, fiddling with the lxc_template.go
file is not sufficient.
See this changelog for some details.
For the record, I had to manually patch src/lxc/start.c; around line 599,
get rid of the SYSERROR("failed to remove CAP_SYS_BOOT capability") error
message.
However, with more recent versions of the LXC tools, this is no longer necessary! This section is kept just for historical purposes.
Make sure that:
- you have a bridge in the container (well, the Docker daemon should automatically take care of that!)
-
/var/lib/dockeris not AUFS - cgroups are mounted
- you have a patched LXC inside the container (this is no longer necessary)
dind is Docker-in-Docker; it's a Dockerfile and wrapper script to provide Docker in Docker easily. Don't hesitate to try it, and if it doesn't work for you, please report your Docker version, OS version, kernel version, so we can fix it!