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

PKS Clusters Fail to Pull Harbor Images (77193)

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

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

PKS clusters fail to pull images from the Harbor registry.

You see messages similar to the following kubelet.stderr.log from the worker node.

E0112 19:28:39.804868   13305 kuberuntime_image.go:51] Pull image "Harbor_FQDN.domain.local/library/my_image:lastest" failed: rpc error: code = Unknown desc = Error response from daemon: Get https://Harbor_FQDN.domain.local/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

You see messages similar to the following in the docker.stderr.log file on the worker node:

time="2020-01-12T19:28:39.803914271Z" level=error msg="Handler for POST /v1.38/images/create returned error: Get https://Harbor_FQDN.domain.local/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"

All services show running for harbor. Errors are not seen in the Harbor logs. Docker instances in subnets outside of the PKS node IP pool might be able to pull images.

Cause

Generally this is caused by a network issue. One can be that the internal container network that Harbor uses overlaps with the PKS cluster node IP pool and so responses stay internal to Harbor instead of leaving back to the PKS cluster worker node.

Resolution

Validate that the internal container IPs are overlapping the PKS cluster worker IPs. Use bosh ssh to ssh to the harbor-app. Then run the following.

sudo su -
cd /var/vcap/packages/docker/bin/
./docker -H unix:///var/vcap/sys/run/docker/dockerd.sock network inspect $(./docker -H unix:///var/vcap/sys/run/docker/dockerd.sock network ls -q)|grep -B1 "Gateway"

If the PKS cluster and Harbor internal networks overlap then set the "Address pool1 base" to a subnet that does not overlap with the node IP block. This is done in the OpsMan UI in the Harbor Tile Networking for customized container network settings. For details  See the section "Configure Networking " in the harbor documentation.

The PKS node IP block range can be checked in the NSX-T UI in the IPAM settings under the advanced network menu settings.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
コンテンツ ライブラリから複数の仮想マシンをデプロイすると、ユーザー インターフェイスに別の vCenter Server のカスタム仕様が表示される (77172)

KB
•
无法关闭分配池组织 VDC 的弹性。PVDC 的主集群上无法容纳所有分配池组织 VDC (77177)

KB
•
提供 Horizon Cloud Service on Microsoft Azure 的 Microsoft Azure 区域 (77121)

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