Online – Ready to Connect
Posted: Sun Apr 06, 2025 8:34 am
Finally we scroll down to the section Hosted. The deployment policy is by default “Allow redeploy”. Since this is a releases repository, and we don't want to overwrite existing artifacts, we have to select “ Disable redeploy ” here, so all artifacts become write-once.
Press “ Create repository ” to finish.
The snapshot repository
Create a new repository. Select type docker (hosted) and name it “ docker-snapshots ”.
In the section Repository connectors, we mark the http checkbox, and enter the number 8083 in the data field behind the checkbox.
Leave all other settings at default.
Press “ Create repository ” to finish.
Aggregating into a single repository
Create a new repository. Select type docker (group) and name it “ docker-public ”.
In the section Repository connectors, we mark the http checkbox, and enter the number 8084 in the data field behind the checkbox.
Scroll down to the bottom and the other three docker repositories to the group. The order is important here. Nexus will try to find artifacts by trying the repositories from top to bottom. At the top should be docker-releases, then docker-snapshots and finally docker-hub. Add all three and make sure the order is correct.
Press “ Create repository ” to finish.
Summary
We have now added four repositories, as shown in the table below
Name
Type
Format
Status
Purpose
docker-central
proxy
docker
Proxy towards docker.io so that we can use public docker images as if they were part of our repository
docker-public
group
docker
Online
One central access point for pulling docker images, regardless of the physical telegram data repository where they are stored
docker-releases
hosted
docker
Online
A repository for our final builds. These docker images are protected from accidental overwriting
docker snapshots
hosted
docker
Online
A repository for our development builds. These docker images can be pushed repeatedly, providing easy of use during development
Security in Nexus
Before we can access the repositories, we will have to set up some permissions. We will start by creating a role for docker.
Press “ Create repository ” to finish.
The snapshot repository
Create a new repository. Select type docker (hosted) and name it “ docker-snapshots ”.
In the section Repository connectors, we mark the http checkbox, and enter the number 8083 in the data field behind the checkbox.
Leave all other settings at default.
Press “ Create repository ” to finish.
Aggregating into a single repository
Create a new repository. Select type docker (group) and name it “ docker-public ”.
In the section Repository connectors, we mark the http checkbox, and enter the number 8084 in the data field behind the checkbox.
Scroll down to the bottom and the other three docker repositories to the group. The order is important here. Nexus will try to find artifacts by trying the repositories from top to bottom. At the top should be docker-releases, then docker-snapshots and finally docker-hub. Add all three and make sure the order is correct.
Press “ Create repository ” to finish.
Summary
We have now added four repositories, as shown in the table below
Name
Type
Format
Status
Purpose
docker-central
proxy
docker
Proxy towards docker.io so that we can use public docker images as if they were part of our repository
docker-public
group
docker
Online
One central access point for pulling docker images, regardless of the physical telegram data repository where they are stored
docker-releases
hosted
docker
Online
A repository for our final builds. These docker images are protected from accidental overwriting
docker snapshots
hosted
docker
Online
A repository for our development builds. These docker images can be pushed repeatedly, providing easy of use during development
Security in Nexus
Before we can access the repositories, we will have to set up some permissions. We will start by creating a role for docker.