Skip to content
This repository has been archived by the owner on May 13, 2021. It is now read-only.

registry pod may failed to start in v0.5.0 #235

Open
bitsf opened this issue Oct 16, 2020 · 0 comments
Open

registry pod may failed to start in v0.5.0 #235

bitsf opened this issue Oct 16, 2020 · 0 comments
Labels
bug Something isn't working

Comments

@bitsf
Copy link
Collaborator

bitsf commented Oct 16, 2020

In v0.5.0 there's a known issue that sometimes when deploy harbor, that pod sz-harbor-cluster-harbor-registry-68974d455d-27c5t container registry may failed to start, and in log it will report parse /etc/registry/config.yaml failed or not found.
The workaround is delete and redeploy harbor, it usually will be success.

An issue also tracked in repo harbor-operator goharbor/harbor-operator#85
@bitsf bitsf added the bug Something isn't working label Oct 16, 2020
@bitsf bitsf mentioned this issue Dec 8, 2020
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bitsf