Closed Razniak closed 1 year ago
Hi @Razniak , which Harbor version you were using? And how do you using the application and generating the pull command
?
This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days.
This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days.
This issue was closed because it has been stalled for 30 days with no activity. If this issue is still relevant, please re-open a new issue.
Hi, we have a problem with pulling the image from the repository, it's not a critical problem, but we are wondering why this is happening. When using the application and generating the pull command, we get: harbor-d.com:443/commons/bsk-rhel9-java17-tomcat10@sha256:6803c02da7753e78ca23206b53b7cd682059abb298a477a8893277856f8f88d1 and it doesn't work properly, we get (Error response from daemon: unauthorized: unauthorized to access repository: commons/bsk-rhel9-java17-tomcat10, action: pull: unauthorized to access repository: commons/bsk-rhel9-java17-tomcat10, action: pull), but when we remove the port from the link: docker pull harbor-d.com/commons/bsk-rhel9-java17-tomcat10@sha256:6803c02da7753e78ca23206b53b7cd682059abb298a477a8893277856f8f88d1, everything starts working as it should. So can you tell why harbor generates such pull link and should it? Or how can we fix it?