Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explore alternatives to device mapper storage driver for Docker. #6

Open
smrubin opened this issue Jun 21, 2017 · 2 comments
Open

Explore alternatives to device mapper storage driver for Docker. #6

smrubin opened this issue Jun 21, 2017 · 2 comments

Comments

@smrubin
Copy link
Contributor

smrubin commented Jun 21, 2017

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: moby/moby#3182 (comment).

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.

@smrubin smrubin created this issue from a note in Movement (Backlog) Jun 21, 2017
@bamb00
Copy link

bamb00 commented Jul 21, 2017

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

@smrubin
Copy link
Contributor Author

smrubin commented Jul 21, 2017

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Movement
Backlog
Development

No branches or pull requests

2 participants