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

This article mainly introduces "the configuration process of using Nexus as a container image warehouse". In daily operation, I believe that many people have doubts about the configuration process of using Nexus as a container image warehouse. The editor consulted all kinds of materials and sorted out simple and easy-to-use operation methods. I hope it will be helpful to answer the doubts of "using Nexus as the configuration process of container image warehouse". Next, please follow the editor to study!

Over the past decade, developers have undergone a shift in the way applications and underlying operating systems are packaged and deployed. The increased use of Docker containers and the most popular open source container orchestration system Kubernetes (K8) has changed the software supply chain. On the one hand, development, test, and production teams can gain the advantage of packaging code and all its dependencies into containers. On the other hand, with the emergence of each new technology, there is a new complexity of packaging management system.

Open source and containerization have redesigned an efficient value stream that can build multiple types of applications for many types of ecosystems, but how do organizations use several different common sources (or registries) to store, manage and deploy their containerized applications?

Simplified container management for Docker,Helm and Kubernetes

Built on a wide range of enterprise storage capabilities, Nexus Repository is a powerful registry for all Docker images and Helm Chart repositories. Supported by a broad user community, Nexus Repository deploys more than 5 million instances and supports more than 1200 organizations-more than 600 large enterprise customers worldwide. Teams can choose to use Nexus Repository OSS's high-performance and completely free container registry, or Nexus Repository Pro when enterprise scalability and functionality are needed.

Unlike Docker Hub or Helm, the development team uses Nexus Repository as the central access point for all public registries, providing a more efficient and stable solution for container management. In addition to integration throughout the CI/CD build pipeline, there are many benefits to using a fully supported enterprise container registry.

Multiple repository types

Nexus repositories support Docker images and Helm 3 repositories through Proxy,Hosted and Group repositories, allowing users to use advanced container management capabilities across development teams.

Proxy repository-reduces repeated downloads and increases download speed for developers and CI servers by setting up a proxy repository for the remote registry of Docker Hub or any other Docker image. Cache images locally to speed up time to market and ensure local access control.

Managed repository-use the Nexus repository to upload your own container images and third-party images to the private Docker registry. The fine-grained permissions of these registries provide enhanced security for development teams and organizations.

Repository Group-allows users to extract images from all repositories in the group without any other client configuration after initial setup. The group repository allows you to use a single URL of the tool to access the aggregated content of multiple agents and managed repositories.

Create a Docker image repository

Create a repository of type Hosted and set HTTP mode access to port 8090.

Update Neuxs Service and add port 8090.

ApiVersion: v1 kind: Service metadata: name: nexus3 namespace: devops labels: k8s-app: nexus3 spec: selector: k8s-app: nexus3 ports:-name: web port: 8081 targetPort: 8081-name: web2 port: 8083 targetPort: 8083-name: docker port: 8090 targetPort: 8090

Update Neuxs Ingress and set the domain name to registry.idevops.site

-host: registry.idevops.site http: paths:-path: / backend: serviceName: nexus3 servicePort: 8090

If you look at the Nexus pod log, you will find that it has been started.

Log in to the image repository

# # default HTTPS prompts error [root@zeyang-nuc-service ~] # docker login registry.idevops.site Username: admin Password: Error response from daemon: Get https://registry.idevops.site/v2/: dial tcp 192.168.1.230 docker 443: connect: connection refused # # Update docker configuration [root@zeyang-nuc-service ~] # vim / etc/docker/daemon.json {"exec-opts": ["native.cgroupdriver=systemd"] "registry-mirrors": ["https://c9ojlmr5.mirror.aliyuncs.com"]," insecure-registries ": [" 192.168.1.200 registry.idevops.site "]} [root@zeyang-nuc-service ~] # systemctl daemon-reload [root@zeyang-nuc-service ~] # systemctl restart docker # # log in to [root@zeyang-nuc-service ~] # docker login registry.idevops.site Username: admin Password: WARNING! Your password will be stored unencrypted in / root/.docker/config.json. Configure a credential helper to remove this warning. See https://docs.docker.com/engine/reference/commandline/login/#credentials-store Login Succeeded

Test upload image

[root@zeyang-nuc-service ~] # docker tag mysql:5.7 registry.idevops.site/library/mysql:5.7 [root@zeyang-nuc-service ~] # docker push registry.idevops.site/library/mysql:5.7 The push refers to repository [registry.idevops.site/library/mysql] c187f0dccfe2: Pushed a45abaac81d1: Pushed 71c5f5690aef: Pushed 8df989cb6670: Pushed f358b00d8ce7: Pushed ae39983d39c4: Pushed b55e8d7c5659: Pushed e8fd11b2289c: Pushed e9affce9cbe8: Pushed 316393412e04: Pushed d0f104dc0a1f: Pushed 5.7: digest: sha256:55638620c5a206833217dff4685e0715fb297a8458aa07c5fe5d8730cc6c872f size: 2621

Verify in nexus.

Nexus acts as a container registry that powers enterprises through Docker and Helm registries for container storage management and K8s deployment. As the DevOps team grows, it is critical to rely on accurate reporting on the quality of open source components in the application. Nexus Lifecycle provides developers and security experts with open source component intelligence on security vulnerabilities, license risks, and architecture quality. Organizations looking for a fully integrated generic container-managed registry and the most accurate component intelligence can use the Nexus platform to meet the growing needs of containerization and open source governance.

At this point, the study on "the configuration process of using Nexus as a container image repository" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

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.