Access Docker proxies via remote runner
This topic explains how to configure access to Nexus Docker proxy repositories from a remote runner. This setup is required for CI/CD pipelines or automated jobs that run in a remote environment and need to pull Docker images from Nexus proxies.
Prerequisites
- AWS account access with permissions to manage Route 53 hosted zones.
- Knowledge of the VPC endpoint associated with the target Nexus Docker proxy (for example
docker-k8s,docker-scr). - Target Docker proxy repository identified. See Nexus proxy repositories for the list of available proxies.
Steps
Log in to your AWS account and open the Route 53 service.
Select the Hosted zone that will resolve the Nexus Docker proxy domain.
Create a DNS record that points the Docker proxy domain to the VPC endpoint associated with the proxy repository.
Example
docker-k8s.ship.gov.sg → vpce-xxxx.amazonaws.com
From your remote runner, test pulling a Docker image from the proxy repository to verify connectivity.
Example
docker pull nexus-docker-k8s.ship.gov.sg/library/nginx:latest
- Confirm that the runner can reach the proxy without errors.
Things to note
- This setup is only required for remote runners. Systems with direct access to Nexus do not require this configuration.
- Ensure the hosted zone and VPC endpoint are correctly configured to avoid connectivity issues.
