Add DRIVERS.md for implemented docker-registry drivers #677
Conversation
|
I like it, let's merge it :-) |
Add DRIVERS.md for implemented docker-registry drivers
|
Thanks @dmp42 . I'm also implementing the driver for our backend storage. It would be better to add more annotation in docker-registry-core so that I can know the meaning of all the methods. |
|
@tobegit3hub if you are not aware about that, we are starting "from scratch" with a new registry, implemented in go. The dev branch is here https://github.com/docker/docker-registry/tree/next-generation The PR that merged (a couple minutes ago!) the new driver interface was here: #643 The new documentation about v2 storage drivers is here: And the expected timeline is to release production ready registry by Q1 2015. ... my point being: storage drivers for V1 are perfectly ok, and the V1 registry is here to stay for some time (#612), but the future is in V2. Now, for v1, the best approach is to mimick one of the (very good) drivers, like elliptics. |
| * [docker-registry-driver-swift](https://github.com/bacongobbler/docker-registry-driver-swift) | ||
| * [docker-registry-driver-qiniu](https://github.com/zhangpeihao/docker-registry-driver-qiniu) | ||
| * [docker-registry-driver-hdfs](https://github.com/lyda/docker-registry-driver-hdfs) | ||
| * [docker-registry-driver-sinastorage](https://github.com/kerwin/docker-registry-driver-sinastorage) |
There was a problem hiding this comment.
Oh yeah, can you please add @noxiouz elliptics driver to the list? (and remove my own gcs implementation, which is kind of crap)
There was a problem hiding this comment.
Of course, I will update this immediately.
Now some developers have implemented the excellent drivers for docker-registry. I think the official repository should display all the verified drivers so that everyone can choose what drivers they want.
For simplicity, I just add DRIVERS.md and the anchor in README.md 😸