New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pushing image to self-hosted Harbor fails with unknown blob
and unauthorized: authentication required
errors
#18611
Comments
Oh, by the way, I have read some previous issues and removed all |
How did you deploy your harbor instance? Is it via offline-installer or harbor-helm? |
Yes, I can consistently reproduce it. I'm using an offline-installer. Below is the output of
|
I have tried other images and encountered similar issues. For example, when pushing
Interestingly, all of these errors occur after the |
As you mentioned |
I've solved my issue, which was due to two misconfigurations. For the
|
I've created a self-hosted Harbor instance and set up a project named
test
. I encountered an issue when trying to push images from my local computer (Windows) using WSL (Ubuntu):When I try to run
docker push my.harbor.com/test/example:v1
, I get the following output:However, when I try to run
docker push my.harbor.com/test/path/example:v1
, I get this output:I logged in with the admin account, and I can confirm that I was successfully authenticated. The token's validity period is 30 minutes, so it has not expired. This issue is consistently reproducible, as the error always occurs when the
Pushing
step is completed, regardless of how many times I try.Additionally, I set up two layers of Nginx forwarding in front of Harbor, using a self-signed SSL certificate (which I've already trusted on my local computer). I've also configured AWS S3 storage for Harbor.
The text was updated successfully, but these errors were encountered: