storj / docker-registry

Docker registry with Storj backend

Docker registry with Storj DCS backend

This repository contains a fork of https://github.com/distribution/distribution with a custom storage driver, supporting Storj decentralized cloud.

Can be tested with starting local registry:

docker run -p 9999:5000 -e REGISTRY_STORAGE=storj -e REGISTRY_STORAGE_STORJ_BUCKET=docker -e REGISTRY_STORAGE_STORJ_ACCESSGRANT=$(cat /tmp/grant) storjlabs/docker-registry

And pushing/pulling image locally:

docker push localhost:9999/elek/herbstag

The image will be stored in the Storj bucket

The driver is also available in this PR: distribution/distribution#3638

Which is blocked by waiting for better extension support.

We're thinking about making these pluggable and and separating them into dedicated GH repos where they could be maintained by folks with the right expertise in the specific storage driver area.

This work is originally started by Michal Niewrzal at https://github.com/mniewrzal/distribution.

Development

Project can be built inside a docker container with docker buildx:

docker buildx build --push -t storjlabs/docker-registry .

(Note: push also pushes the image to DockerHub)

Original README starts here.

The toolset to pack, ship, store, and deliver content.

This repository's main product is the Open Source Registry implementation for storing and distributing container images using the OCI Distribution Specification. The goal of this project is to provide a simple, secure, and scalable base for building a large scale registry solution or running a simple private registry. It is a core library for many registry operators including Docker Hub, GitHub Container Registry, GitLab Container Registry and DigitalOcean Container Registry, as well as the CNCF Harbor Project, and VMware Harbor Registry.

This repository contains the following components:

Component	Description
registry	An implementation of the OCI Distribution Specification.
libraries	A rich set of libraries for interacting with distribution components. Please see godoc for details. Note: The interfaces for these libraries are unstable.
documentation	Docker's full documentation set is available at docs.docker.com. This repository contains the subset related just to the registry.

How does this integrate with Docker, containerd, and other OCI client?

Clients implement against the OCI specification and communicate with the registry using HTTP. This project contains a client implementation which is currently in use by Docker, however, it is deprecated for the implementation in containerd and will not support new features.

What are the long term goals of the Distribution project?

The Distribution project has the further long term goal of providing a secure tool chain for distributing content. The specifications, APIs and tools should be as useful with Docker as they are without.

Our goal is to design a professional grade and extensible content distribution system that allow users to:

• Enjoy an efficient, secured and reliable way to store, manage, package and exchange content
• Hack/roll their own on top of healthy open-source components
• Implement their own home made solution through good specs, and solid extensions mechanism.

Contribution

Please see CONTRIBUTING.md for details on how to contribute issues, fixes, and patches to this project. If you are contributing code, see the instructions for building a development environment.

Communication

For async communication and long running discussions please use issues and pull requests on the github repo. This will be the best place to discuss design and implementation.

For sync communication we have a #distribution channel in the CNCF Slack that everyone is welcome to join and chat about development.

Licenses

The distribution codebase is released under the Apache 2.0 license. The README.md file, and files in the "docs" folder are licensed under the Creative Commons Attribution 4.0 International License. You may obtain a copy of the license, titled CC-BY-4.0, at http://creativecommons.org/licenses/by/4.0/.

docker-registry's Issues

img.dev.storj.io doesn't allow to push new images

docker push img.dev.storj.io/dev/checkerng
Using default tag: latest
The push refers to repository [img.dev.storj.io/dev/checkerng]
74c4981f3a0b: Layer already exists 
3b0573825467: Layer already exists 
b530df93bb93: Layer already exists 
dc049a46d1b4: Layer already exists 
b9672b062964: Layer already exists 
fa39d522708b: Layer already exists 
822ee476c182: Layer already exists 
4ff4865fda68: Layer already exists 
c9552617ed8e: Layer already exists 
f26de0c16474: Layer already exists 
a502b4e0c279: Layer already exists 
ed834f4d5944: Layer already exists 
30768046a6f2: Layer already exists 
f4554cc614c8: Layer already exists 
051c408be63b: Layer already exists 
8d70467291d4: Layer already exists 
d925e0fae4e6: Layer already exists 
received unexpected HTTP status: 500 Internal Server Error