Shulou(Shulou.com)06/03 Report--

This article shows the solution to the inability to synchronize mirroring between harbor. The solution is simple and easy to master, if you encounter this problem in your daily work. I hope you can find a solution to your questions through this article.

One: background

The two harbor (An and B) in the test environment cannot synchronize the image. The reason for the check is that the harbor container cannot properly resolve the ip address of the peer harbor. As a result, the image synchronization of the harbor added in the repository management whose status is unhealthy,harbor cannot be performed properly.

Second: solution

Add B's ip to each container in A's harbor to resolve to / etc/hosts. Also do a similar operation in B, with the following command:

A) execute the following command on server A to add harbor resolution of B to each container of harbor: `for i in `docker ps | grep harbor | awk'{print $1}'`; do docker exec-it $I bash-c 'echo "domain name of 10.203.121.137 Bharbor" > > / etc/hosts'; domain `b) execute the following command on server B to add harbor resolution of A to each container of harbor: for i in `docker ps | grep harbor | awk' {print $1}'` Do docker exec-it $I bash-c 'echo "10.203.121.60 Aharbor domain name" > > / etc/hosts';done

Three: remarks

The relevant commands have been recorded in / etc/rc.local on the server.

This is the end of the solution to the inability to synchronize mirrors between harbor. Solving the problem is not just the method analyzed in this article, but the accuracy of the analysis in this article is beyond doubt. If you like this article, you might as well share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.