There are many queries to "registry-1.docker.io".

Products

• VMware NSX

Issue/Introduction

• You see a log in the NSX Manager syslog indicating that a query to "registry-1.docker.io" failed.

var/log/syslog

yyyy-mm-ddThh:mm:ss nsx01 dockerd 2589 - -  time="yyyy-mm-ddThh:mm:ss" level=warning msg="Error getting v2 registry: Get \"https://registry-1.docker.io/v2/\": dial tcp xx.xx.xx.xx:443: i/o timeout"
yyyy-mm-ddThh:mm:ss nsx01 dockerd 2589 - -  time="yyyy-mm-ddThh:mm:ss" level=info msg="Attempting next endpoint for pull after error: Get \"https://registry-1.docker.io/v2/\": dial tcp xx.xx.xx.xx:443: i/o timeout"
yyyy-mm-ddThh:mm:ss nsx01 dockerd 2589 - -  time="yyyy-mm-ddThh:mm:ss" level=error msg="Handler for POST /v1.25/images/create returned error: Get \"https://registry-1.docker.io/v2/\": dial tcp xx.xx.xx.xx:443: i/o timeout"
yyyy-mm-ddThh:mm:ss nsx01 nsx-metrics-agents 936456 - -  Get "https://registry-1.docker.io/v2/": dial tcp xx.xx.xx.xx:443: i/o timeout

 

• The NSX Manager is not connected to an external network.

Environment

• VMware NSX 4.1.x

Cause

The docker image "nsbu-docker-images/metrics_mux:4.1.1" does not exist locally.
Therefore, NSX Manager queries the external "registry-1.docker.io".
If NSX Manager is not connected to the external network, a large number of logs will be output to the syslog indicating that the query failed.

Resolution

You can stop queries to "registry-1.docker.io" by stopping nsx-metrics-agents.

nsx-metrics-agents is an unnecessary service in nsx 4.1.
There is no impact if you stop it.

1.  Log in to the NSX Manager CLI as the root user.
2.  Stop the nsx-metrics-agents with the following command:
   systemctl stop nsx-metrics-agents
   
   
3. It will get started after reboot again, to disable them use below command:
   systemctl disable nsx-metrics-agents