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

VCH unable to pull images using "docker pull" from docker hub (74686)

Last Updated: 10/27/2020Categories: TroubleshootingTotal Views: 3313Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

While trying to pull an image from docker hub using the docker pull <image name> command, you see an error similar to the following:

Using default tag: latest
Error response from daemon: Head https://registry-1.docker.io/v2/: x509: certificate signed by unknown authority

VCH is configured to use a proxy server for internet connectivity

The configured proxy server has SSL termination enabled, You can verify this using a command similar to curl -x <proxy URL> -v <Destination website URL> from any machine using the same proxy. In the output, look for Issuer details and you should see the proxy host details rather than actual Issuer of the certificate for that particular website

Resolution

When VCH tries to pull an image from docker hub off the internet, the traffic passes through the proxy server. during the SSL termination process, the proxy server adds its own CA chain to the docker hub certificate. This CA chain is not recognized by the VCH.

To resolve this you need to reconfigure the VCH to use the proxy server's root CA chain as a registry CA. A command similar to the following can be used to reconfigure the VCH:

vic-machine-operating_system configure
--target vcenter_server_address/dc1
--user [email-masked]
--password password
--compute-resource cluster1
--registry-ca /home/admin/mycerts/ca.crt
--name vch1
--thumbprint certificate_thumbprint
--no-tlsverify

Related Information

Configure Registry Access

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
ホット パッチを適用した後、使用量メーターがログ バンドルのエクスポートに失敗し、暗号化されていないレポートを送信する (74693)

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
在 VMware NSX-T Controller 节点上，/var/log 分区呈指数增长，而不进行轮换 (74758)

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 vSphere Integrated Containers

VMware vSphere

Related Versions:

VMware vSphere Integrated Containers 1.5.x

Take Our Survey

Support Assistant