Background
After the harbor is built locally and relevant configurations are made, an error is still reported: error response from daemon: login attempt to http://10.xx.xx.xx:8000/v2/ Failed with status: 403 Forbidden. Where http://10.xx.xx.xx:8000 This is the website of harbor service I built
Premises
First, find the following log according to the command: systemctl status docker
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Find the docker configuration file through the log, change * * execstart =/usr/bin/dockerd * * to the following in the/lib/SYSTEMd/system/docker.service file and save it:
ExecStart=/usr/bin/dockerd --insecure-registry=10.xx.xx.xx:8000
Restart after configuration:
sudo systemctl daemon-reload && sudo systemctl restart docker
Settle
After configuration, run the docker login command:
docker login 10.xx.xx.xx:8000 -u admin -p Harbor12345
The error “403 Forbidden” is still reported. The error may be that docker does not recognize the web address of harbor service and adds an agent to handle the web address. At this time, you need to delete the http-proxy.conf and https-proxy.conf files in the/etc/SYSTEMd/system/docker. Service. D directory
after I delete the above files, login succeeds
Similar Posts:
- An error is reported when the docker command is executed in Jenkins
- Job for docker.service failed because the control process exited with error code. See “syste…
- [Solved] Failed to start Docker Application Container Engine.
- Harbor 443 connect connection refused [How to Solve]
- [Solved] Docker error: Error starting daemon: Error initializing network controller: list bridge addresses failed: no available network
- [Solved] Docker Starup Error: Failed to start Docker Application Container Engine.
- A dependency job for docker.service failed
- Docker Cannot Start: Failed to start Docker Application Container Engine
- An error is reported in the dockerfie image, and the status is acitvating (start)
- Record the problem that docker cannot be started once