Ok makes sense,
at which level do you see the go-docker thing?
Something like
golang.docker.io/go-docker/docker/client
or
golang.docker.io/docker/go-docker/client
The second could be trivial in case that the user import the top level package (which doesn’t currently exist)