Pushing Container with robot account ends with 500 (internal server error) #19567
-
I am trying to push a container image with a robot account created in Harbor, but the push fails with status code 500. I have created the robot-account as admin and is able to access 3 projects, 2 of them I have configured as proxy cache and address dockerhub and the nvidia container registry respectively, the robot-account can only read from these projects. A third project serves as a local storage location, so the account can read and write from it (pull and push). The pull of a small test image via the proxy cache worked as intended. However, after the corresponding tagging and the push to save the image in the targeted project in the registry, it fails with status code 500. The Version of Harbor is 2.7.1 The logs from the harbor-registry does not show any problems:
I can see some errors in the harbor-core container, but it doesn't help me.
|
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 1 reply
-
|
Beta Was this translation helpful? Give feedback.
-
@reisman234 |
Beta Was this translation helpful? Give feedback.
-
With the admin account, I had the same problem. What did you mean with JSON payload from the robot account ?
To start redis again, I moved the dump.rdb file, which worked so fare that the containers (redis, core, job...) could start again. But now there are missing projects and users, which cannot be created again because the UI throwing error "they are already existing". |
Beta Was this translation helpful? Give feedback.
-
Since nobody but me currently uses the registry and only containers were stored which were built by a CI pipeline, it is probably easier to simply reinstall Harbor than to tinker with databases. Also, the current error has nothing to do with the initial discussion. |
Beta Was this translation helpful? Give feedback.
@reisman234 So this issue has nothing to do with the robot account.
I guess there was something wrong with the DB container.