-
Notifications
You must be signed in to change notification settings - Fork 241
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
Pull fixes from moby/storage #104
Comments
Right now we have been concentrating on Overlay driver (overlay2 in Moby). But we plan on adding more support for devicemapper and perhaps replacing it with a new lvm based driver going forward. |
These have been all back ported, I believe. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sorry if I misunderstand intention of this project, looks like it is aiming to implement docker features in a docker-independent way, yet it reuses a lot of docker code.
There were few fixes done do docker graphdrivers year ago, which I can find in a current codebase, which is worrying, how this project is meant to be supported and go forward? If there is no development resources allocated to evolve storage drivers, maybe worth reexporting everything from docker graphdrivers?
Example of missing PRs are :
The text was updated successfully, but these errors were encountered: