Assumptions
- You are comfortable with Linux, Docker and Helm
- You have a fundamental understanding how Nexus Repository 3 works
Helm OCI Support
Nexus Repository 3 does not currently support Helm OCI proxy repositories (URL with "OCI://").
There is an existing Product Idea for this to be addressed in a future release:
https://ideas.sonatype.com/ideas/IDEAS-I-1989 Add OCI support for both hosted Helm repositories and proxied Helm repositories
Workaround - Use Docker Proxy instead
However, we do provide support for Docker "OCI" images in Nexus Repository 3, but you cannot use the "OCI" protocol in a proxy repository.
Instead, in Nexus Repository 3 you need to use the "HTTPS" protocol.
For example, if you require to use the "oci://registry-1.docker.io/bitnamicharts/" as the location of the remote repository to be proxied, then you will need to create a docker proxy repository with the following remote storage:-
https://registry-1.docker.io/
Considerations for a Docker repository
The Docker API requires /v2 to be at the context root. To reconcile the two requirements, you can use a number of approaches:
- A reverse proxy to map /v2 requests to /repository/docker-ghcr-proxy/v2/.
Please refer to https://help.sonatype.com/repomanager3/nexus-repository-administration/formats/docker-registry/docker-repository-reverse-proxy-strategies
- Subdomain routing.
Please refer to https://help.sonatype.com/repomanager3/nexus-repository-administration/formats/docker-registry/docker-subdomain-connector
- Docker connector ports.