That said, devicemapper is tested and certified on RHEL and centos, so if you're on Ubuntu I have no visibility into the level of support they make available. You can certainly use AUFS if you prefer.
On Feb 10, 2016, at 3:42 PM, Philippe Lafoucrière < philippe.lafoucri...@tech-angels.com> wrote: On Wed, Feb 10, 2016 at 11:47 AM, Scott Dodson <sdod...@redhat.com> wrote: > If you're not using centos/rhel packages give this a try, I've not > followed this myself but it looks sane > > https://docs.docker.com/engine/userguide/storagedriver/device-mapper-driver/#configure-direct-lvm-mode-for-production > According to this doc, we're using devicemapper + direct-lvm (no "Data loop fils" in docker info, nor "Metadata loop file"). We have started the container on a dedicated VM, with AUFS, and the problem is gone. We have panicked each node where this container was started, so I guess "devicemapper + direct-lvm" is not also a viable option :( _______________________________________________ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
_______________________________________________ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
