Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Image pull fails when pulled from a user-created project in Harbor (71076)

Last Updated: 7/19/2019Categories: InformationalTotal Views: 23915Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

You see an error similar to the following when attempting to pull an image from a user-created project in Harbor:

rpc error: code = Unknown desc = Error response from daemon: pull access denied for harbor-registry/usercreatedproject/image:tag, repository does not exist or may require 'docker login'

Cause

By default, when a project is created in Harbor it is created in "private" access mode. In this mode, a user would have to run docker login before pulling images under this project.

Resolution

If you want to allow only selected users to have pull access, you can grant access by authenticating that user to the Registry.

You can login to the Harbor registry by running a command similar to the following:

docker login <Registry name> -u username

Enter the password and then you will see a successful login message similar to the following:

========
WARNING! Your password will be stored unencrypted in /root/.docker/config.json.
Configure a credential helper to remove this warning. See
https://docs.docker.com/engine/reference/commandline/login/#credentials-store

Login Succeeded
========

If the Project has to be granted READ access to all the users, set the Access Level of the project to "Public".
When a project is set to public, anyone has read permission to the repositories under this project, and the user does not need to run docker login"before pulling images under this project.
For pushing the Images, the user has to run docker login to the registry and then authenticate successfully.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
将 CA 签名的 SSL 证书应用于嵌入式 Orchestrator 端口 8283 (71060)

KB
•
移除智能卡时在 Ubuntu 18.4、16.4、SLED12SP3、SLES12SP3 和 SLED11SP4 上自动锁定屏幕 (71068)

KB
•
在启用了 UAC 的 Windows 上无法安装 vRealize Operations Manager 7.5 Telegraf 代理 (70780)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware PKS

Related Versions:

VMware PKS 1.x

Take Our Survey

Support Assistant