Explore alternatives to device mapper storage driver for Docker.

Open smrubin opened this issue 8 years ago • 2 comments

The device-mapper storage driver with docker doesn't clean up after itself well enough and appears to have a memory leak, see GitHub issue here: https://github.com/docker/docker/issues/3182#issuecomment-256532928.

We should explore an alternative to the device-mapper, such as AUFS or Overlay and use that instead in our environments to keep them lean.

Jun 21 '17 19:06 smrubin

Is this target to loop-lvm and direct-lvm?

Jul 21 '17 15:07 bamb00

Right now loop-lvm is being used with devicemapper. If we want to continue using devicemapper, we should configure direct-lvm for production.

Although, I am not opposed to investigating overlay2 or aufs in place of devicemapper, as those are recommended in the docs and are suitable for our environment.

Jul 21 '17 18:07 smrubin