You can create as many repos as you need and group them all in the group repo. This will group all the above repos and provide you a single URL to configure your clients to download from/deploy to.Ĭreate a new Docker (group) repository and configure it like: Next time you download the same dependency, it will be cached in your Nexus.Ĭreate a new Docker (proxy) repository and configure it like: private repoĪ repository for Docker images that your team creates.Ĭreate a new Docker (hosted) repository and configure it like:Ī repository that proxies everything you download from the official registry, Docker Hub. I had some problems with slightly older versions of Docker, so I strongly suggesting you to start with the version that I’ve tested with, that is 1.12.3. We are going to use 8082 for pull from the proxy repo and 8083 for pull and push to the private repo. Important to notice: the Docker repo requires 2 different ports.

In my use case I had to configure it with HTTP, because we didn’t have the certificate nor the knowledge on how to obtain it. But this is not mandatory for it to work.īy default, the Docker client communicates with the repo using HTTPS.

That way, the data for every repo will be in a different folder in /nexus-data (inside the Docker container). I suggest you to create a new blob store for each new repo you want to create.

create a group repository to provide all the above repos under a single URL.

create a proxy repository pointing to Docker Hub.

create a private (hosted) repository for our own images.

Just do that and the installation is done. This is the third and last part of a series of posts on Nexus 3 and how to use it as repository for several technologies.Ĭheck out the first part of this series to see how we installed and ran Nexus 3 using a single docker command.

Install nexus docker