Hello, Gilles. >> Docker tries to use aufs as storage (for /var/lib/docker). >> aufs is not in the Debian kernel. >> >> The easiest way I find was to configure Docker to use overalyfs instead. >> >> Here comes the second problem : systemd. >> >> With sysvinit, you simply hav to put a launch option in >> /etc/default/docker : >> DOCKER_OPTS="-s overlay" >> >> With systemd, you have to overrid the service configuration, and if you >> want to use /etc/default/docker, here's how to do it : >> >> Create /etc/systemd/system/docker.service.d/overlayfs.conf with that >> content : >> [Service] >> EnvironmentFile=-/etc/default/docker >> ExecStart= >> ExecStart=/usr/bin/docker daemon -H fd:// $DOCKER_OPTS > I tried to add DOCKER_OPTS in /etc/default/docker. Then I changed the > Init file based on your suggestion: > > ------------------------------------------------------------------- > # cat /etc/default/docker | grep DOCKER_OPTS > # Use DOCKER_OPTS to modify the daemon startup options. > #DOCKER_OPTS="--dns 8.8.8.8 --dns 8.8.4.4" > DOCKER_OPTS="-s overlay" > ------------------------------------------------------------------- > # cat /lib/systemd/system/docker.service > [Unit] > Description=Docker Application Container Engine > Documentation=https://docs.docker.com > After=network.target docker.socket > Requires=docker.socket > > [Service] > Type=notify > # the default is not to use systemd for cgroups because the delegate > issues still > # exists and systemd currently does not support the cgroup feature set > required > # for containers run by docker > > #### DGB - 20160708 #### > EnvironmentFile=-/etc/default/docker > #ExecStart=/usr/bin/docker daemon -H fd:// > ExecStart=/usr/bin/docker daemon -H fd:// $DOCKER_OPTS > #### DGB - 20160708 #### > > MountFlags=slave > LimitNOFILE=1048576 > LimitNPROC=1048576 > LimitCORE=infinity > TimeoutStartSec=0 > # set delegate yes so that systemd does not reset the cgroups of docker > containers > Delegate=yes > > [Install] > WantedBy=multi-user.target > ------------------------------------------------------------------- > > But it seems that the file system is not recognized: > > ------------------------------------------------------------------- > Jul 8 15:41:12 orion docker[4838]: > time="2016-07-08T15:41:12.933967003-03:00" level=info msg="New > containerd process, pid: 4844\n" > Jul 8 15:41:13 orion docker[4838]: > time="2016-07-08T15:41:13.938943525-03:00" level=error msg="'overlay' > not found as a supported filesystem on this host. Please ensure kernel > is new enough and has overlay support loaded." > Jul 8 15:41:13 orion docker[4838]: > time="2016-07-08T15:41:13.939091971-03:00" level=fatal msg="Error > starting daemon: error initializing graphdriver: driver not supported" > Jul 8 15:41:13 orion systemd[1]: docker.service: main process exited, > code=exited, status=1/FAILURE > Jul 8 15:41:13 orion docker[4838]: time="2016-07-08T15:41:13-03:00" > level=info msg="stopping containerd after receiving terminated" > Jul 8 15:41:13 orion systemd[1]: Failed to start Docker Application > Container Engine. > Jul 8 15:41:13 orion systemd[1]: Unit docker.service entered failed state. > ------------------------------------------------------------------- From what I've read here [1], it seems that this filesystem was introduced with Linux 3.18. And I'm using here 3.16: # uname -a Linux orion 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08) x86_64 GNU/Linux Are you using the kernel of Backports? Kind regards, Daniel [1] https://docs.docker.com/engine/userguide/storagedriver/overlayfs-driver/
Attachment:
signature.asc
Description: OpenPGP digital signature