-
Notifications
You must be signed in to change notification settings - Fork 0
HarborTroubleshooting
Running docker logs {container ID} on Harbor containers identified via docker container ls does not produce anything useful.
Instead, navigate to /var/log/harbor/ and browse the .log files in that directory.
It's quite possible that Harbor has not installed quite correctly: the browser error messages are not very helpful here. For example, try to register a new user - you will be told that a perfectly reasonable email address is not valid.
To check that Harbor is in fact installed correctly, SSH into the machine and run docker container ls a few times. If the status of some "goharbor/..." containers is consistently "Restarting" then Harbor has not quite installed correctly.
Read the log files (see section above) to bug-fix your configuration and re-install.
It may also be worth restarting the system (see below) to see if this resolves the issue.
If the Docker containers that Harbor runs in were in an intermediate state when the machine went down, then they may not have restarted correctly upon machine reboot.
SSH into the machine and run the following commands:
cd /usr/local/harbor/
sudo docker-compose restart
If restarting Harbor does not solve the problem, then a re-install may be necessary. This should not affect the data stored in databases, etc, but it is still worth doing a backup beforehand.
cd /usr/local/harbor/
bash install.sh
The latest versions of docker and containered currently have a conflict causing the following error to occur when installing harbor:
...OCI runtime create failed: container_linux.go:344: starting container process caused \"process_linux.go:297: getting the final child\\'s pid from pipe caused \\\\\"read init-p: connection reset by peer\\\\\"\": unknown'\n\nERROR: for log Cannot start service log: b'OCI runtime create failed: container_linux.go:344: starting container process caused \"process_linux.go:297: getting the final child\\'s pid from pipe caused \\\\\"read init-p: connection reset by peer\\\\\"\": unknown'\nEncountered errors while bringing up the project...
This can be resolved by running:
sudo yum downgrade -y containerd.io-1.2.2-3.el7