3 ms·
Naively I would have thought a docker registry with on-disk storage managed by ipfs would have been a low-effort way to meet this requirement. Unfortunately yo
by hardwaresofton 8y ago
Naively I would have thought a docker registry with on-disk storage managed by ipfs would have been a low-effort way to meet this requirement.
Unfortunately you'd need something to manage the pinning settings, but it feels like a relatively small addition to some other registry that could be hacked together in a small amount of time.
- deleted 8y ago[deleted]
- zcw100 8y agoYou mean something like ipfs cluster? https://cluster.ipfs.io https://cluster.ipfs.io
- hardwaresofton 8y agoI didn't know ipfs cluster existed -- thanks for the reference. I was more thinking of a harbor[0] like cobbling of these technologies together -- harbor combines a bunch of F/OSS tools into one powerful registry solution. Here are a few: - Distribution for storing images - Notary for signing - Clair for static analysis Based on this I was thinking of was basically Distribution + ipfs cluster + a small management daemon. The daemon is only there to tie the other pieces together and present a unified interface but the bulk of the work can be done with the other pieces. [0]: https://github.com/goharbor/harbor/wiki/Architecture-Overview-of-Harbor https://github.com/goharbor/harbor/wiki/Architecture-Overvie... [1]: https://github.com/docker/distribution https://github.com/docker/distribution [2]: https://github.com/theupdateframework/notary https://github.com/theupdateframework/notary [3]: https://github.com/coreos/clair https://github.com/coreos/clair