You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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.
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: