-
Notifications
You must be signed in to change notification settings - Fork 18.9k
Move the daemon/graphdriver package to storage #9758
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
Conversation
Even though we refer to them commonly as "storage drivers" and they are used by more subsystems than just the daemon package - the container, image, and volume storage library is buried under the daemon package and is called `graphdriver` which is a very generic name. Also, some types it exposes like `graphdriver.Driver` is a stutter and is not idiomatic Go. This change moves the `daemon/graphdriver` package to the top-level of the `github.com/docker/docker` package tree under the name `storage`. Users of this package now deal with `storage.Driver` objects! And other subsystems which use it, like the `graph` package (another unfortunate name), have one fewer thing they have to reach into the `daemon` package for. All references to `graphdriver` (with the exception of environment variables and Go build tags) have been updated to use the new package location. Docker-DCO-1.1-Signed-off-by: Josh Hawn <[email protected]> (github: jlhawn)
|
@shykes @jfrazelle @LK4D4 @crosbymichael @erikh @vieux @icecrime @tianon @unclejack If you think this is a good idea, I would also like to propose moving a couple of other packages as well:
|
|
Oh, I'm +100 for graph :) |
|
oh! and @tiborvass ^ |
|
hey so I looked back in the history and it turns out that |
|
|
|
and even before that |
|
sure 👍 |
Even though we refer to them commonly as "storage drivers" and they are used
by more subsystems than just the daemon package - the container, image, and
volume storage library is buried under the daemon package and is called
graphdriverwhich is a very generic name. Also, some types it exposes likegraphdriver.Driveris a stutter and is not idiomatic Go.This change moves the
daemon/graphdriverpackage to the top-level of thegithub.com/docker/dockerpackage tree under the namestorage. Users of thispackage now deal with
storage.Driverobjects! And other subsystems which useit, like the
graphpackage (another unfortunate name), have one fewer thingthey have to reach into the
daemonpackage for.All references to
graphdriver(with the exception of environment variablesand Go build tags) have been updated to use the new package location.