Docker5 full-featured harbor warehouse construction process

Docker5 full-featured harbor warehouse construction process

Harbor is an enterprise-level registry server for storing and distributing Docker images. It can be used to build an enterprise-wide Docker image repository. Based on Docker's open source project Distribution, it adds some functional features needed by enterprises, such as image synchronization replication, vulnerability scanning, and permission management. Harbor is an enterprise-level Docker Registry management project open sourced by VMware. It includes functions such as permission management (RBAC), LDAP, log auditing, management interface, self-registration, image replication, and Chinese support.

Build a full-featured repository that supports anonymous pulls

[root@server1 mnt]# cd compose/
[root@server1 compose]# ls
docker-compose-Linux-x86_64-1.16.1 docker-compose-Linux-x86_64-1.24.1
docker-compose-Linux-x86_64-1.22.0 docker-compose-Linux-x86_64-1.27.0
[root@server1 compose]# mv docker-compose-Linux-x86_64-1.27.0 /usr/local/bin/docker-compose
[root@server1 compose]# chmod +x /usr/local/bin/docker-compose
[root@server1 mnt]# tar zxf harbor-offline-installer-v1.10.1.tgz

Resolve dependencies and unzip harbor

vim harbor.yml

In the harbor directory

insert image description here

The location of the authentication and key must be written correctly

./install.sh

Execute script installation

Creating redis ... done
Creating harbor-core ... done
Creating nginx ... done
Creating harbor-jobservice ... done
✔ ----Harbor has been installed and started successfully.----

done

[root@server1 harbor]# docker-compose

The docker-compose command must be executed in the harbor directory

[root@server1 harbor]# docker-compose start
[root@server1 harbor]# docker-compose ps
      Name Command State Ports                                  
--------------------------------------------------------------------------------------------------------------------------------------------
harbor-core /harbor/harbor_core Up (healthy)                                                                           
harbor-db /docker-entrypoint.sh Up (healthy) 5432/tcp                                                                
harbor-jobservice /harbor/harbor_jobservice ... Up (healthy)                                                                           
harbor-log /bin/sh -c /usr/local/bin/ ... Up (healthy) 127.0.0.1:1514->10514/tcp                                               
harbor-portal nginx -g daemon off; Up (healthy) 8080/tcp                                                                
nginx nginx -g daemon off; Up (healthy) 0.0.0.0:80->8080/tcp,:::80->8080/tcp,                                   
                                                                    0.0.0.0:443->8443/tcp,:::443->8443/tcp                                  
redis redis-server /etc/redis.conf Up (healthy) 6379/tcp                                                                
registry /home/harbor/entrypoint.sh Up (healthy) 5000/tcp                                                                
registryctl /home/harbor/start.sh Up (healthy)

Make sure the mirrors are up and enter the IP address directly in the browser

insert image description here

User admin, password yume

insert image description here

[root@server1 docker]# docker logout reg.westos.org
Removing login credentials for reg.westos.org
[root@server1 docker]# docker login reg.westos.org
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

Log out of the previous login and log in again. This is the information saved in the database.
It was not created locally.

[root@server1 docker]# docker tag yakexi007/game2048:latest reg.westos.org/library/game2048:latest
[root@server1 docker]# docker push reg.westos.org/library/game2048:latest  
The push refers to repository [reg.westos.org/library/game2048]
88fca8ae768a: Pushed 
6d7504772167: Pushed 
192e9fad2abc: Pushed 
36e9226e74f8: Pushed 
011b303988d2: Pushed 
latest: digest: sha256:8a34fb9cb168c420604b6e5d32ca6d412cb0d533a826b313b190535c03fe9390 size: 1364

Upload to the warehouse and view

insert image description here

[root@server2 docker]# cat daemon.json 
{
  "registry-mirrors": ["https://reg.westos.org"]
}

In server2, the private warehouse has been pointed to

Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Registry Mirrors:
  https://reg.westos.org/
 Live Restore Enabled: false

And it is effective to do address resolution in server2

insert image description here

[root@server2 docker]# docker pull reg.westos.org/library/game2048:latest
latest: Pulling from library/game2048
534e72e7cedc: Pull complete 
f62e2f6dfeef: Pull complete 
fe7db6293242: Pull complete 
3f120f6a2bf8: Pull complete 
4ba4e6930ea5: Pull complete 
Digest: sha256:8a34fb9cb168c420604b6e5d32ca6d412cb0d533a826b313b190535c03fe9390
Status: Downloaded newer image for reg.westos.org/library/game2048:latest
reg.westos.org/library/game2048:latest

The image pushed from server1 is successfully pulled down on server2

insert image description here

It can be seen from the log that anonymous users pulled

[root@server1 docker]# docker tag yakexi007/nginx:latest reg.westos.org/library/nginx:latest
[root@server1 docker]# docker push reg.westos.org/library/nginx
The push refers to repository [reg.westos.org/library/nginx]
3bd8699f28ba: Pushed 
1d3b68b6972f: Pushed 
de1602ca36c9: Pushed 
latest: digest: sha256:5ea5a786e978abd8e6e0b6c0f37f7271be19c40d6b8247b1d9dae70c1fbab9eb size: 949

Upload an nginx image again in server1

insert image description here

You can see

[root@server2 docker]# docker pull nginx
Using default tag: latest
latest: Pulling from library/nginx
cfb92865f5ba: Pull complete 
8dd350b5e0d5: Pull complete 
15157df2751c: Pull complete 
Digest: sha256:5ea5a786e978abd8e6e0b6c0f37f7271be19c40d6b8247b1d9dae70c1fbab9eb
Status: Downloaded newer image for nginx:latest
docker.io/library/nginx:latest

Server2 pulls nginx again, done
2. Use harbor repository, some basic instructions

[root@server1 harbor]# docker-compose logs

View logs

[root@server1 harbor]# docker-compose stop

Deactivate a warehouse
3. Maintain the warehouse (add warehouse module: automatic image scanning, signature function)
Stop the warehouse first

[root@server1 harbor]# docker-compose rm

Delete all containers. Next, add the harbor function. Check the help of the installation script. You can see three modules: image vulnerability scanning, content trust, and remote login. Add the module name after the installation script. After reinstalling, these module functions will be enabled.

[root@server1 harbor]# ./install.sh --help

Note: Please set hostname and other necessary attributes in harbor.yml first. DO NOT use localhost or 127.0.0.1 for hostname, because Harbor needs to be accessed by external clients.
Please set --with-notary if needs enable Notary in Harbor, and set ui_url_protocol/ssl_cert/ssl_cert_key in harbor.yml bacause notary must run under https. 
Please set --with-clair if needs enable Clair in Harbor
Please set --with-chartmuseum if needs enable Chartmuseum in Harbor
[root@server1 harbor]# ./install.sh --with-notary --with-clair --with-chartmuseum
[Step 5]: starting Harbor ...
Creating network "harbor_harbor-clair" with the default driver
Creating network "harbor_harbor-notary" with the default driver
Creating network "harbor_harbor-chartmuseum" with the default driver
Creating network "harbor_notary-sig" with the default driver
Creating harbor-log ... done
Creating registry ... done
Creating harbor-db ... done
Creating registryctl ... done
Creating redis ... done
Creating chartmuseum ... done
Creating harbor-portal ... done
Creating harbor-core ... done
Creating notary-signer ... done
Creating clair ... done
Creating clair-adapter ... done
Creating notary-server ... done
Creating nginx ... done
Creating harbor-jobservice ... done
✔ ----Harbor has been installed and started successfully.----
[root@server1 harbor]# docker-compose ps
      Name Command State Ports                             
--------------------------------------------------------------------------------------------------------------------------------------------
chartmuseum ./docker-entrypoint.sh Up (health: starting) 9999/tcp                                                       
clair ./docker-entrypoint.sh Up (health: starting) 6060/tcp, 6061/tcp                                             
clair-adapter /clair-adapter/clair-adapter Up (health: starting) 8080/tcp                                                       
harbor-core /harbor/harbor_core Up (health: starting)                                                                  
harbor-db /docker-entrypoint.sh Up (health: starting) 5432/tcp                                                       
harbor-jobservice /harbor/harbor_jobservice ... Up (health: starting)                                                                  
harbor-log /bin/sh -c /usr/local/bin/ ... Up (health: starting) 127.0.0.1:1514->10514/tcp                                      
harbor-portal nginx -g daemon off; Up (health: starting) 8080/tcp                                                       
nginx nginx -g daemon off; Up (health: starting) 0.0.0.0:4443->4443/tcp,:::4443->4443/tcp,                      
                                                                             0.0.0.0:80->8080/tcp,:::80->8080/tcp,                          
                                                                             0.0.0.0:443->8443/tcp,:::443->8443/tcp                         
notary-server /bin/sh -c migrate-patch - ... Up                                                                                     
notary-signer /bin/sh -c migrate-patch - ... Up                                                                                     
redis redis-server /etc/redis.conf Up (health: starting) 6379/tcp                                                       
registry /home/harbor/entrypoint.sh Up (health: starting) 5000/tcp                                                       
registryctl /home/harbor/start.sh Up (health: starting)

Use ps to check and you will find some more functions to log in to 172.25.250.11

insert image description here
insert image description here

These were not there before the reinstall.

--with-notary --with-clair --with-chartmuseum
They are content trust, image scanning and charts library. When viewing the image information in the browser, you can see that the image is followed by scanning, signature and other information. Because the image scanning and signature functions are not enabled when configuring this directory, the current displayed image is unscanned and unsigned.

insert image description here

How to automatically scan images?

insert image description here

Select Remember to save and try again, upload an image again

[root@server1 harbor]# docker tag rhel7:latest reg.westos.org/library/rhel7:latest

This time, use the rhel7 image and change the name first.

[root@server1 harbor]# docker push reg.westos.org/library/rhel7:latest 
The push refers to repository [reg.westos.org/library/rhel7]
18af9eb19b5f: Pushed 
latest: digest: sha256:58cd9120a4194edb0de4377b71bd564953255a1422baa1bbd9cb23d521c6873b size: 528

Upload to harbor

insert image description here

When I opened the browser, I found that it had been automatically scanned.

How to implement the image signing function?

insert image description here

When content trust is selected, try to pull the rhel7 image just uploaded on server2

[root@server2 ~]# docker pull rhel7
Using default tag: latest
Error response from daemon: pull access denied for rhel7, repository does not exist or may require 'docker login': denied: requested access to the resource is denied

If you uncheck content trust, you can pull normally because the repository has content trust enabled. The client can only download signed images, but the debian image in the repository is not signed. Therefore, the client fails to pull.
Although the pull of the harbor repository failed, the system will automatically pull the image from the Internet (now in an offline environment, so the above error occurs)

Now we need to authorize the signature of the trusted image. First, delete the previously uploaded image in the web interface. For the image without signature, set two environment variables on the Docker server. Then, we can use the content trust function to sign the uploaded image.
(1) Deploy root certificate

[root@server1 harbor]# docker-compose ps
      Name Command State Ports                                  
--------------------------------------------------------------------------------------------------------------------------------------------
chartmuseum ./docker-entrypoint.sh Up (healthy) 9999/tcp                                                                
clair ./docker-entrypoint.sh Up (healthy) 6060/tcp, 6061/tcp                                                      
clair-adapter /clair-adapter/clair-adapter Up (healthy) 8080/tcp                                                                
harbor-core /harbor/harbor_core Up (healthy)                                                                           
harbor-db /docker-entrypoint.sh Up (healthy) 5432/tcp                                                                
harbor-jobservice /harbor/harbor_jobservice ... Up (healthy)                                                                           
harbor-log /bin/sh -c /usr/local/bin/ ... Up (healthy) 127.0.0.1:1514->10514/tcp                                               
harbor-portal nginx -g daemon off; Up (healthy) 8080/tcp                                                                
nginx nginx -g daemon off; Up (healthy) 0.0.0.0:4443->4443/tcp,:::4443->4443/tcp,                               
                                                                    0.0.0.0:80->8080/tcp,:::80->8080/tcp,                                   
                                                                    0.0.0.0:443->8443/tcp,:::443->8443/tcp                                  
notary-server /bin/sh -c migrate-patch - ... Up                                                                                     
notary-signer /bin/sh -c migrate-patch - ... Up                                                                                     
redis redis-server /etc/redis.conf Up (healthy) 6379/tcp                                                                
registry /home/harbor/entrypoint.sh Up (healthy) 5000/tcp                                                                
registryctl /home/harbor/start.sh Up (healthy)

Port 4443 is used for signing

[root@server1 harbor]# export DOCKER_CONTENT_TRUST=1
[root@server1 harbor]# export DOCKER_CONTENT_TRUST_SERVER=https://reg.westos.org:4443

(2) Enable Docker content trust

[root@server1 harbor]# docker push reg.westos.org/library/nginx:latest
The push refers to repository [reg.westos.org/library/nginx]
3bd8699f28ba: Layer already exists 
1d3b68b6972f: Layer already exists 
de1602ca36c9: Layer already exists 
latest: digest: sha256:5ea5a786e978abd8e6e0b6c0f37f7271be19c40d6b8247b1d9dae70c1fbab9eb size: 949
Signing and pushing trust metadata
Error: error contacting notary server: x509: certificate signed by unknown authority

Latest must be added, which indicates an updated version. (3) An error occurred when uploading again. There is no certificate in the hidden directory .docker. Create a certificate directory tls. After entering the directory, create a directory with the same name as the container, reg.westos.org:4443.
Copy the previously generated certificate to this directory

[root@server1 ~]# cd .docker/
[root@server1 .docker]# ls
config.json trust
[root@server1 .docker]# mkdir tls
[root@server1 .docker]# cd tls/
[root@server1 tls]# mkdir reg.westos.org:4443
[root@server1 tls]# cd reg.westos.org\:4443/
[root@server1 reg.westos.org:4443]# cp /docker /
.autorelabel data/ etc/ lib64/ opt/ run/ sys/ var/          
bin/ dev/ home/ media/ proc/ sbin/ tmp/          
boot/ docker lib/ mnt/ root/ srv/ usr/          
[root@server1 reg.westos.org:4443]# cp /root/data/certs/westos.org.crt ca.crt
[root@server1 reg.westos.org:4443]# ls
ca.crt

(4) Try uploading again

[root@server1 harbor]# docker push reg.westos.org/library/nginx:latest 
The push refers to repository [reg.westos.org/library/nginx]
3bd8699f28ba: Layer already exists 
1d3b68b6972f: Layer already exists 
de1602ca36c9: Layer already exists 
latest: digest: sha256:5ea5a786e978abd8e6e0b6c0f37f7271be19c40d6b8247b1d9dae70c1fbab9eb size: 949
Signing and pushing trust metadata
You are about to create a new root signing key passphrase. This passphrase
will be used to protect the most sensitive key in your signing system. Please
choose a long, complex passphrase and be careful to keep the password and the
The key file itself is secure and backed up. It is highly recommended that you use a
password manager to generate the passphrase and keep it safe. There will be no
way to recover this key. You can find the key in your config directory.
Enter passphrase for new root key with ID dbac0cb: 
Passphrase is too short. Please use a password manager to generate and store a good random passphrase.
Enter passphrase for new root key with ID dbac0cb: 
Passphrase is too short. Please use a password manager to generate and store a good random passphrase.
Enter passphrase for new root key with ID dbac0cb: 
Passphrase is too short. Please use a password manager to generate and store a good random passphrase.
Enter passphrase for new root key with ID dbac0cb: 
Passphrase is too short. Please use a password manager to generate and store a good random passphrase.
Enter passphrase for new root key with ID dbac0cb: 
Repeat passphrase for new root key with ID dbac0cb: 
Enter passphrase for new repository key with ID a868e96: 
Repeat passphrase for new repository key with ID a868e96: 
Finished initializing "reg.westos.org/library/nginx"
Successfully signed reg.westos.org/library/nginx:latest

After solving the problem, the server uploads the image again. To successfully upload a new image, the administrator needs to set the root key and warehouse key.
(Note that each time you upload a different version of the image, you only need to enter the corresponding warehouse key, not the root key)
After setting it up, go to the web interface to check and find that the signature of the uploaded image is displayed as successful

insert image description here

Signed, must add latest

[root@server2 ~]# docker pull nginx
Using default tag: latest
latest: Pulling from library/nginx
cfb92865f5ba: Pull complete 
8dd350b5e0d5: Pull complete 
15157df2751c: Pull complete 
Digest: sha256:5ea5a786e978abd8e6e0b6c0f37f7271be19c40d6b8247b1d9dae70c1fbab9eb
Status: Downloaded newer image for nginx:latest
docker.io/library/nginx:latest

There is no problem pulling the signed image on server2. If it is not signed and content trust is enabled, it still does not work. Try the feasibility again, delete 2048 from harbor first, then delete the previously downloaded 2048 image on server2, and pull it again, and an error will be reported.

[root@server2 ~]# docker pull game2048
Using default tag: latest
Error response from daemon: pull access denied for game2048, repository does not exist or may require 'docker login': denied: requested access to the resource is denied

Then server1 pushes 2048 again

[root@server1 harbor]# docker push reg.westos.org/library/game2048:latest 
The push refers to repository [reg.westos.org/library/game2048]
88fca8ae768a: Layer already exists 
6d7504772167: Layer already exists 
192e9fad2abc: Layer already exists 
36e9226e74f8: Layer already exists 
011b303988d2: Layer already exists 
latest: digest: sha256:8a34fb9cb168c420604b6e5d32ca6d412cb0d533a826b313b190535c03fe9390 size: 1364
Signing and pushing trust metadata
Enter passphrase for root key with ID dbac0cb: 
Enter passphrase for new repository key with ID 18c8514: 
Repeat passphrase for new repository key with ID 18c8514: 
Finished initializing "reg.westos.org/library/game2048"
Successfully signed reg.westos.org/library/game2048:latest

insert image description here

Already signed, server2 pulls again

[root@server2 ~]# docker pull game2048
Using default tag: latest
latest: Pulling from library/game2048
534e72e7cedc: Pull complete 
f62e2f6dfeef: Pull complete 
fe7db6293242: Pull complete 
3f120f6a2bf8: Pull complete 
4ba4e6930ea5: Pull complete 
Digest: sha256:8a34fb9cb168c420604b6e5d32ca6d412cb0d533a826b313b190535c03fe9390
Status: Downloaded newer image for game2048:latest
docker.io/library/game2048:latest

done

4. Guest users access undisclosed repositories
(1) Create a new project

insert image description here

[root@server1 harbor]# export DOCKER_CONTENT_TRUST=0

Turn off content trust, otherwise you will be in trouble

[root@server1 harbor]# docker tag reg.westos.org/library/game2048:latest reg.westos.org/haoge/game2048:latest
[root@server1 harbor]# docker push reg.westos.org/haoge/game2048

Re-upload a 2048 image for the new project haoge

insert image description here

[root@server2 ~]# docker pull reg.westos.org/haoge/game2048:latest
Error response from daemon: pull access denied for reg.westos.org/haoge/game2048, repository does not exist or may require 'docker login': denied: requested access to the resource is denied

Server2 pulls 2048 from haoge, reports an error, needs to log in

insert image description here

Create a new user

insert image description here

In the haoge project, give the user wqh a guest identity

[root@server2 ~]# docker login reg.westos.org
Username: wqh
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

server2 login wqh
Pull again

[root@server2 ~]# docker pull reg.westos.org/haoge/game2048:latest
latest: Pulling from haoge/game2048
Digest: sha256:8a34fb9cb168c420604b6e5d32ca6d412cb0d533a826b313b190535c03fe9390
Status: Downloaded newer image for reg.westos.org/haoge/game2048:latest
reg.westos.org/haoge/game2048:latest
[root@server2 ~]# docker images 
REPOSITORY TAG IMAGE ID CREATED SIZE
nginx latest 2560dbd4ee1e 14 months ago 31.1MB
game2048 latest 19299002fdbe 4 years ago 55.5MB
reg.westos.org/haoge/game2048 latest 19299002fdbe 4 years ago 55.5MB

No problem, but push is not allowed because visitors do not have permission.

insert image description here

The log shows that wqh just pulled a mirror and finally:
Remove image scanning and signature functions, which speed up disk consumption (scanning speeds up disk consumption)
(Subsequent experiments do not require image scanning and signing)

[root@server1 harbor]# docker-compose stop
Stopping harbor-jobservice ... done
Stopping nginx ... done
Stopping notary-server ... done
Stopping clair-adapter ... done
Stopping notary-signer ... done
Stopping clair ... done
Stopping harbor-core ... done
Stopping chartmuseum ... done
Stopping harbor-portal ... done
Stopping redis ... done
Stopping registryctl ... done
Stopping harbor-db ... done
Stopping registry ... done
Stopping harbor-log ... done
[root@server1 harbor]# docker-compose rm
Going to remove harbor-jobservice, nginx, notary-server, clair-adapter, notary-signer, clair, harbor-core, chartmuseum, harbor-portal, redis, registryctl, harbor-db, registry, harbor-log
Are you sure? [yN] y
Removing harbor-jobservice ... done
Removing nginx ... done
Removing notary-server ... done
Removing clair-adapter ... done
Removing notary-signer ... done
Removing clair ... done
Removing harbor-core ... done
Removing chartmuseum ... done
Removing harbor-portal ... done
Removing redis ... done
Removing registryctl ... done
Removing harbor-db ... done
Removing registry ... done
Removing harbor-log ... done
[root@server1 harbor]# ./install.sh --with-chartmuseum 

[Step 0]: checking if docker is installed ...

Note: docker version: 19.03.15

[Step 1]: checking docker-compose is installed ...

Note: docker-compose version: 1.27.0

[Step 2]: loading Harbor images ...
Loaded image: goharbor/clair-adapter-photon:v1.0.1-v1.10.1
Loaded image: goharbor/harbor-jobservice:v1.10.1
Loaded image: goharbor/redis-photon:v1.10.1
Loaded image: goharbor/notary-server-photon:v0.6.1-v1.10.1
Loaded image: goharbor/clair-photon:v2.1.1-v1.10.1
Loaded image: goharbor/harbor-log:v1.10.1
Loaded image: goharbor/registry-photon:v2.7.1-patch-2819-2553-v1.10.1
Loaded image: goharbor/notary-signer-photon:v0.6.1-v1.10.1
Loaded image: goharbor/chartmuseum-photon:v0.9.0-v1.10.1
Loaded image: goharbor/harbor-registryctl:v1.10.1
Loaded image: goharbor/nginx-photon:v1.10.1
Loaded image: goharbor/harbor-migrator:v1.10.1
Loaded image: goharbor/prepare:v1.10.1
Loaded image: goharbor/harbor-portal:v1.10.1
Loaded image: goharbor/harbor-core:v1.10.1
Loaded image: goharbor/harbor-db:v1.10.1


[Step 3]: preparing environment ...

[Step 4]: preparing harbor configs ...
prepare base dir is set to /mnt/harbor
Clearing the configuration file: /config/log/logrotate.conf
Clearing the configuration file: /config/log/rsyslog_docker.conf
Clearing the configuration file: /config/nginx/conf.d/notary.upstream.conf
Clearing the configuration file: /config/nginx/conf.d/notary.server.conf
Clearing the configuration file: /config/nginx/nginx.conf
Clearing the configuration file: /config/core/env
Clearing the configuration file: /config/core/app.conf
Clearing the configuration file: /config/registry/config.yml
Clearing the configuration file: /config/registry/root.crt
Clearing the configuration file: /config/registryctl/env
Clearing the configuration file: /config/registryctl/config.yml
Clearing the configuration file: /config/db/env
Clearing the configuration file: /config/jobservice/env
Clearing the configuration file: /config/jobservice/config.yml
Clearing the configuration file: /config/notary/server-config.postgres.json
Clearing the configuration file: /config/notary/server_env
Clearing the configuration file: /config/notary/signer_env
Clearing the configuration file: /config/notary/signer-config.postgres.json
Clearing the configuration file: /config/notary/notary-signer.key
Clearing the configuration file: /config/notary/notary-signer.crt
Clearing the configuration file: /config/notary/notary-signer-ca.crt
Clearing the configuration file: /config/notary/root.crt
Clearing the configuration file: /config/clair/postgresql-init.d/README.md
Clearing the configuration file: /config/clair/postgres_env
Clearing the configuration file: /config/clair/config.yaml
Clearing the configuration file: /config/clair/clair_env
Clearing the configuration file: /config/clair-adapter/env
Clearing the configuration file: /config/chartserver/env
Generated configuration file: /config/log/logrotate.conf
Generated configuration file: /config/log/rsyslog_docker.conf
Generated configuration file: /config/nginx/nginx.conf
Generated configuration file: /config/core/env
Generated configuration file: /config/core/app.conf
Generated configuration file: /config/registry/config.yml
Generated configuration file: /config/registryctl/env
Generated configuration file: /config/db/env
Generated configuration file: /config/jobservice/env
Generated configuration file: /config/jobservice/config.yml
loaded secret from file: /secret/keys/secretkey
Generated configuration file: /config/chartserver/env
Generated configuration file: /compose_location/docker-compose.yml
Clean up the input dir



[Step 5]: starting Harbor ...
Creating harbor-log ... done
Creating harbor-portal ... done
Creating registryctl ... done
Creating harbor-db ... done
Creating redis ... done
Creating registry ... done
Creating chartmuseum ... done
Creating harbor-core ... done
Creating nginx ... done
Creating harbor-jobservice ... done
✔ ----Harbor has been installed and started successfully.----
[root@server1 harbor]# docker-compose ps
      Name Command State Ports                             
--------------------------------------------------------------------------------------------------------------------------------------------
chartmuseum ./docker-entrypoint.sh Up (health: starting) 9999/tcp                                                       
harbor-core /harbor/harbor_core Up (health: starting)                                                                  
harbor-db /docker-entrypoint.sh Up (health: starting) 5432/tcp                                                       
harbor-jobservice /harbor/harbor_jobservice ... Up (health: starting)                                                                  
harbor-log /bin/sh -c /usr/local/bin/ ... Up (health: starting) 127.0.0.1:1514->10514/tcp                                      
harbor-portal nginx -g daemon off; Up (health: starting) 8080/tcp                                                       
nginx nginx -g daemon off; Up (health: starting) 0.0.0.0:80->8080/tcp,:::80->8080/tcp,                          
                                                                             0.0.0.0:443->8443/tcp,:::443->8443/tcp                         
redis redis-server /etc/redis.conf Up (health: starting) 6379/tcp                                                       
registry /home/harbor/entrypoint.sh Up (health: starting) 5000/tcp                                                       
registryctl /home/harbor/start.sh Up (health: starting)

insert image description here

Final result

The above is the detailed content of docker5 full-featured harbor. For more information about docker harbor, please pay attention to other related articles on 123WORDPRESS.COM!

You may also be interested in:
  • Detailed explanation of building a Docker private image repository based on Harbor
  • Docker builds a private warehouse (registry, harbor)
  • Architecture and component description of docker private library Harbor
  • Detailed steps for installing Harbor, a private Docker repository
  • Implementation of Docker to build private warehouse (registry and Harbor)
  • Example of how to build a Harbor public repository with Docker
  • Docker private warehouse harbor construction process
  • Steps for Docker to build a private warehouse Harbor
  • Docker Gitlab+Jenkins+Harbor builds a persistent platform operation
  • Detailed tutorial on building a continuous integration delivery environment based on Docker+K8S+GitLab/SVN+Jenkins+Harbor
  • How to build a private Docker repository using Harbor
  • Detailed tutorial on installing harbor private warehouse using docker compose
  • Jenkins builds Docker images and pushes them to Harbor warehouse
  • Method of building docker private warehouse based on Harbor
  • Introduction and deployment method of Docker private warehouse Harbor

<<:  MySQL5.7 parallel replication principle and implementation

>>:  Detailed explanation of various methods of Vue component communication

Recommend

Installation tutorial of MySQL 5.7 green version under windows2008 64-bit system

Preface This article introduces the installation ...

How to recompile Nginx and add modules

When compiling and installing Nginx, some modules...

JavaScript to implement login slider verification

This article example shares the specific code of ...

Solution to the problem that Ubuntu cannot connect to the Internet in the virtual machine

It is very painful to set up a virtual machine th...

MySQL free installation version (zip) installation and configuration detailed tutorial

This article shares the installation and configur...

Overview and differences between html inline elements and html block-level elements

Block-level element features : •Always occupies a ...

Which loop is the fastest in JavaScript?

Knowing which for loop or iterator is right for o...

Detailed explanation of Apache SkyWalking alarm configuration guide

Apache SkyWalking Apache SkyWalking is an applica...

Uniapp WeChat applet: Solution to key failure

uniapp code <template> <view> <ima...

Have you really learned MySQL connection query?

1. Inner Join Query Overview Inner join is a very...

Solve the problem that MySQL read-write separation causes data not to be selected after insert

MySQL sets up independent writing separation. If ...

What to do if you forget the initial password when installing MySQL on Mac

Forgetting the password is a headache. What shoul...

In-depth understanding of the core principles of React Native (Bridge of React Native)

In this article we assume you already know the ba...

Add a startup method to Linux (service/script)

Configuration file that needs to be loaded when t...

Introduction and architecture of Apache Arrow, a high-performance data format library package on JVM (Gkatziouras)

Apache Arrow is a popular format used by various ...