Univention Bugzilla – Bug 39418
Configure docker.io to use overlayFS
Last modified: 2015-11-17 12:12:23 CET
Currently docker.io 1.6 uses devicemapper as storage driver: root@master50:~# docker info Containers: 1 Images: 4 Storage Driver: devicemapper We should set '-s overlay' in the DOCKER_OPTS in /etc/default/docker
Maybe we don't want this currently: * Looks like coreOS users found that they run out of inodes with the default bytes-per-inode ratio of 16k/inode, see https://github.com/coreos/bugs/issues/264 . This may cause issues with upgraded UCS systems. * See also https://github.com/docker/docker/pull/12354
About overlayFS see also: https://docs.docker.com/reference/commandline/daemon/#daemon-storage-driver-option But there are issues with dockers default devicemapper setup in loopback mode: * http://www.projectatomic.io/blog/2015/06/notes-on-fedora-centos-and-docker-storage-drivers/ * https://github.com/docker/docker/blob/master/daemon/graphdriver/devmapper/README.md
The new metapackage univention-docker now sets --storage-driver=overlay in /etc/default/docker. Changelog adjusted.
Changelog: OK Installation: OK Upgrade: OK ( you have to reboot)
UCS 4.1 has been released: https://docs.software-univention.de/release-notes-4.1-0-en.html https://docs.software-univention.de/release-notes-4.1-0-de.html If this error occurs again, please use "Clone This Bug".